Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to call module with recommended source url #66

Open
ElizaRayner opened this issue Jun 10, 2021 · 0 comments
Open

Unable to call module with recommended source url #66

ElizaRayner opened this issue Jun 10, 2021 · 0 comments

Comments

@ElizaRayner
Copy link

I am using citizen in an ec2 with the servers being a localhost on port 3000. I successfully published a module using citizen and can see a module.tar.gz file that is created under the path modules/namespace/name/provider/version (note: I have actual values for the url, namespace, name, provider and version but I am referring to them as such for ease of reading). I then attempted to define an instance of the module following the example given and using the source url/namespace/name/provider as shown in the example. This returned a 404 error. All different versions of the source returned either 404 or "no source url returned" except for when the source was in the form: url/v1/modules/tarball/namespace/name/provider/module.tar.gz which works. I get all the same results when using localtunnel, which gives an https url instaed of the localhost http url. I am using the default settings for all environment variables except for the CITIZEN_STORAGE but the results are the same for if I use file or s3 here. Is there a path that does not involve including the tar file and tarball in the path that will not trigger a 404?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant