Sorry for the delayed response, things have been wildly busy for me.
I did configure my domains as instructed, and they do resolve to the expected IP address. I don’t have an already existing reverse proxy, so I was just following along with what the guide was telling me to do. That said, this may be the issue, because I don’t recall seeing any specific set up for the included reverse proxy and I’ve been through that guide 3 times. I haven’t configured port forwarding on my router since I’m using a Hetzner VPS for this, but I did make sure to open up the required ports on the firewall.
Alright that gives me a good idea what your working with.
I am running it along side some other projects, so I already had a reverse proxy set up, so I didn’t look closely at the other parts of the guide in that section.
If you want to be able to use this server for other hosting in the future, you may want to set up a reverse proxy. I can give some advice about that if you’re interested!
In your case, if the only thing you ever want to host on this box is Matrix, you don’t need a reverse proxy. You should be able to do the steps here and it should result in a working deployment.
It looks like that should give you a tls.yaml file, which you need to include when issuing the helm command to deploy everything. This one:
Thanks for your help! It’s very much appreciated. I was thinking I might want to use this VPS for an occasional OwnCast stream and as a SyncThing target, so it sounds like I’ll need a reverse proxy. Any recommendations on something relatively easy to use? I’ve seen people mention ngnix, traefik, caddy and a few others, but I’m not sure which would integrate nicely with ESS. Also, I appreciate the heads up about the helm commands. Definitely important info to have!
Sorry for the delayed response, things have been wildly busy for me.
I did configure my domains as instructed, and they do resolve to the expected IP address. I don’t have an already existing reverse proxy, so I was just following along with what the guide was telling me to do. That said, this may be the issue, because I don’t recall seeing any specific set up for the included reverse proxy and I’ve been through that guide 3 times. I haven’t configured port forwarding on my router since I’m using a Hetzner VPS for this, but I did make sure to open up the required ports on the firewall.
Alright that gives me a good idea what your working with.
I am running it along side some other projects, so I already had a reverse proxy set up, so I didn’t look closely at the other parts of the guide in that section.
If you want to be able to use this server for other hosting in the future, you may want to set up a reverse proxy. I can give some advice about that if you’re interested!
In your case, if the only thing you ever want to host on this box is Matrix, you don’t need a reverse proxy. You should be able to do the steps here and it should result in a working deployment.
It looks like that should give you a tls.yaml file, which you need to include when issuing the helm command to deploy everything. This one:
You need to make sure that in the <optional> section, you include:
So your command would be this, if you have no additional yaml files, and if you do, simply put “-f path/to/file” at the end, right before the “–wait”:
Thanks for your help! It’s very much appreciated. I was thinking I might want to use this VPS for an occasional OwnCast stream and as a SyncThing target, so it sounds like I’ll need a reverse proxy. Any recommendations on something relatively easy to use? I’ve seen people mention ngnix, traefik, caddy and a few others, but I’m not sure which would integrate nicely with ESS. Also, I appreciate the heads up about the helm commands. Definitely important info to have!