How to configure port forwarding?

[apbarratt]

I feel like I'm going round in circles here. No matter what I do, I end up with the same problem telling me that "The server is not reachable on Port 443."

I started with a cloudflare tunnel, gave up on the idea. Was setting up a reverse proxy but figured I didn't actually need it. So I've gone pure and simple. I've launched the docker using the command in the readme and I've gone into my router and set up port forwarding, but absolutely nothing works.

The readme would suggest I only need to forward 443 for TCP and 3478 for TCP and UDP. So that's precisely what I've done.

I've tried pointing WAN 443 to host:443, didn't work. To host:8443, nope. To host:8080 (this worked on the tunnel before to at least show the landing page) nope, not this time.
I've tried forwarding 80, 443, 8080, 8443 to their said same ports on the host.
I recall on the tunnel version I had to tell it not to verify TLS (presumably some clash over certificates seeing as cloudflare provides its own) so I do wonder if there's an issue here.

Come on guys, what am I missing? Surely I'm not the only one trying to set this stuff up on a plain ubuntu box using Cloudflare DNS? :(

[szaimen]

Hello, it might be that you are behind CGNAT and thus not able to open port 443. in this case would cloudflare be a possible solution.

Why did you not continue in #655? This looked promising to me...

[apbarratt]

Nextcloud reports it as such:

Operating System: | Linux 5.4.0-110-generic x86_64
CPU: | Intel(R) Pentium(R) CPU J2900 @ 2.41GHz (4 cores)
Memory: | 3.73 GB

Curious that it's not reporting a full 4GB of ram there, I'd expect that from a 32bit system but not 64 :/
Interesting seeing that it's able to get that information even from within the docker container too.

[apbarratt]

Whelp, it's 22:38 here, so I'm off to bed.
Thank you for all your help these last couple of days. Hopefully I'll figure out the websockets proxying tomorrow and let you go be someone else's saviour 😄

[szaimen]

Curious that it's not reporting a full 4GB of ram there,

That is due to the different counting of 1000 vs 1024...

[szaimen]

Hopefully I'll figure out the websockets proxying tomorrow

All right! Good luck!

[apbarratt]

Righto, got the websockets sorted on nginx and after a full reboot on tiddles, I'm all in order. I'm now very happy with my set up :)
Thank you again, I'll be sure to write up some notes and see if there's anywhere in the docs I could supplement based on them for outsiders like me to get going quicker :)

[apbarratt]

I'm at an utter loss for what's going on. It was working perfectly for a short while there and then, it just stopped. I've tried killing everything, restarting the box, whatever I can think of. But I'm faced simply with the fact that now the only things running are my nginx and nextcloud-aio-mastercontainer containers but absolutely nothing is loading on https://tiddles.local:8080
It simply starts the request and then just sort of hangs there, trying to load. Sometimes I might see the containers page load up after a great many minutes of waiting but just as unresponsive, most times just nothing happens.

I've tried killing all the containers, pruning them all, etc, it's just dead and I cannot for the life of me think what it is I've done to cause this :/

[szaimen]

lets continue in #730