How to force Railway proxy to trust self-signed certs generated by collabora/code

ajhalili2006
HOBBYOP

2 days ago

I am having a bit of headache getting collabora/code running on Railway for my self-hosted Nextcloud instance. If I set -o:ssl.enable=false as part of extra_params environment variable, it would work but it will complain about the protocol mismatch. Do I need a Caddy server (or some other proxy) in between for this if I can't force it?

Also, here's a curl result within the container as I railway ssh there, which is causing gateway timeout errors:

root@906c1a0e5d83:/# curl http://localhost:9980 -i
curl: (52) Empty reply from server
Solved$10 Bounty

3 Replies

Railway
BOT

2 days ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!

danny
PRO

2 days ago

You should automatically get a certificate from Railway when connecting (or generating) a domain. This domain acts as a proxy for your internal traffic.

ajhalili2006
HOBBYOP

2 days ago

I did a bit of digging and found the following extra_params from the Nextcloud Snap installation docs regarding this:

      - extra_params=
      --o:ssl.enable=false  # required to avoid issues with self-signed certs
      --o:ssl.termination=true  # required since we're behind Railway's proxy
      # the rest of the installation configuration via docker-compose
      --o:logging.level=warning
      --o:user_interface.mode=compact

I gone ahead and applied these after formatting them into a single-line and it worked flawlessly. (I will marking this as solution for both future self and others.)

Status changed to Solved brody • 1 day ago

Loading...
How to force Railway proxy to trust self-signed certs generated by collabora/code - Railway Help Station