Are you using a custom domain? Or the Railway domain?

do you think aleks will miss the 10 min window

Probably! 🤣

lets see

And he missed the 10 minute window! 🤣

Custom domain

I'm not seeing that error when I setup a new deploy

843f00ff-8688-41cc-adef-d4920bd94b43

aleks how did you miss the 10 minute window, did you forget about it

I just deployed it a couple of days ago

I got up to walk the dog

aka yes

yeah, I did

oh wait

NEXTCLOUD_TRUSTED_DOMAINS

sorry

ohhhh I need to redeploy it for it to get that var in after setting up a custom domain

dont worry, vin has let that slip his mind too

nope, still not working

Huzzah, I got it working! I filled in the TRUSTED_PROXIES, OVERWRITEHOST, and OVERWRITEPROTOCOL variables from the image

Hello everyone, nice to see you guys are mocking eachother.

Im exploring Nextcloud and I ran into a similiar issue. Ive deployed it, it works from the railway domain. When Ive added the the custom domain in railway I receive this message when I try to access it from the custom domain.

I guess I have to follow aleks's steps to get it running, right? What are the values for TRUSTED_PROXIES, OVERWRITEHOST, and OVERWRITEPROTOCOL? Thank you for patience with my noobish question, please help me what is propably obvious... 😄

this should be what you want, untested though -

TRUSTED_PROXIES=100.0.0.0/8
OVERWRITEHOST=${{RAILWAY_PUBLIC_DOMAIN}}
OVERWRITEPROTOCOL=https

yes that works. thanks!

no problem