This is a question the Railway community is better placed to answer than support: people who have built the same thing and can tell you what actually worked for them.

So we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who answers it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

• Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
• Keep it private and close the thread - Nothing becomes public and the thread closes.

Have you tried performing the action in an incognito browser?

Yes I did

Lemme give that a try

Did it work?

It didnt

not sure why the dropdown keeps snapping back, couldn't find anyone else reporting that exact bug, might just be a glitch, worth trying a refresh or different browser first.

but you don't really need that dropdown to work anyway. just set these env vars yourself on the service, pointing at your bucket's actual credentials: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_STORAGE_BUCKET_NAME, AWS_S3_ENDPOINT_URL, AWS_S3_REGION_NAME, and add AWS_S3_ADDRESSING_STYLE=path (railway needs that one specifically). that's all django-storages needs, the dropdown was just a shortcut for filling those in.

So I have my own way of naming my credentials which are just as what django storages is in the bucket. Because its not matching especially the AWS_STORAGE_BUCKET_NAME, AWS_S3_ENDPOINT_URL with AWS SDK, I get error when uploading files. Error of bucket name not found.

that error usually means the addressing style is wrong, not the variable names themselves. by default boto3/django-storages tries to put the bucket name into the domain itself, like bucketname.endpoint.com, but railway doesn't support that. you need to add one more variable: AWS_S3_ADDRESSING_STYLE=path

that tells it to put the bucket name in the url path instead of the domain, which is what railway actually needs. add that one and re-try the upload.

I actually have that, I changed the namings in the credentials but still changes back to the default of the AWS SDK

Yes thats what I did and worked but what I dont get is why it switched back. I am working on a pypi project here is the link https://pypi.org/project/django-railway-storage/ you can have a look. Now I have to use the generic and django storages both in the project.

Thanks for the help

okay so is your problem resolved now ?? im going to check it out

Yes I have to use both variables in case its resolved in the future