Hey, 

I am pretty new here and I am having difficulties setting up a reverse proxy with letsencrypt. Although spaceinvaders instructions were very clear and I understood every stop along the way, I failed to get it working. I've spent the entire day on it. Googling and repeated attempts (remove letsencrypt and its appdata, redo and verify all steps, reboot server and routers, etc.) have not resulted with any improvements. Please help!

I have done the following to set up the reverse proxy:

1. ✔ Set up duckdns account/docker which points to home WAN (confirmed via ping)
2. ✔ Set up CNAMEs for subdomains to point to duckdns (confirmed via ping)
3. ✔ Router ports: forward WAN 80 -> server 180 and WAN 443 -> server 1443
4. ✔ Docker: Enabled 'Preserve user defined networks' and created custom docker network
5. ✔ Install letsencrypt docker using custom network, ports 180 and 1443, my email/domain/subdomains, only subdomains set to true (log shows successful cert creation for all * subdomains and server ready, which confirms all previous steps)

6. ✔ Nextcloud, currently working on internal network. Modify for letsencrypt:

   • Set container to same custom network as letsencrypt
   • create appdata/letsencrypt/nginx/proxy-confs/nextcloud.subdomain.conf from sample file, no changes needed.
   • edit appdata/nextcloud/www/nextcloud/config/config.php with notepad++ and add lines:

   • 1 => 'nextcloud.xxxxxxxx.com',
   • 'overwrite.cli.url' => 'https://nextcloud.xxxxxxxx.com',
   • 'overwritehost' => 'nextcloud.xxxxxxxx.com',
   • 'overwriteprotocol' => 'https',

7. ✔ I then restarted both letsencrypt and nextcloud containers, clicked nextcloud/WebUI. The webUI opened very quickly and displayed the address as https://nextcloud.xxxxxxxx.com. Everything is appearing successful!

8. I am pleased at this point and about to test the setup further. The successful feeling doesn't last long.

9. X I take my phone off the home wireless and try to access https://nextcloud.xxxxxxxx.com and it just never loads ("took too long to respond, err_connection_timed_out"). Returning to my PC, I try to access the nextcloud webUI again and it now displays the same error I saw on my phone. Not only this, but now my plex server now shows as "Not available outside your network" (32400 is forwarded to the server and had previously been working fine with no issues). Logs of nextcloud and letsencrypt show no issues. Restarting the plex container does not resolve the network issues, but restarting the server machine does; however, the problem repeats if I attempt to use nextcloud again. This sounds like the router firewall dropping packets to me, so I try to disable the firewall completely, no change.

This definitely sounds like a networking issue with unraid or, more likely, the router/firewall (ATT, Arris BGW210). I have attached logs from the router firewall and the unraid diagnostics file.

 

What can I do? How else can I troubleshoot this further? Thank you all so much.

 

Edit: Deleted attachments.

 

 

Edited August 20, 20187 yr by jarch3r

Update: To anyone curious, from the symptoms, it was clearly a networking/firewall issue. I did finally get this working, but not with the ISP provided router; even with all firewall settings disabled on the ISP router, it would not work.

 

To get it working, I set my ISP router into bridge mode, exposing the ISP WAN IP to a real router (edgerouter x) to avoid double NAT and set it up as normal from there.

On 8/20/2018 at 7:58 PM, jarch3r said:

Update: To anyone curious, from the symptoms, it was clearly a networking/firewall issue. I did finally get this working, but not with the ISP provided router; even with all firewall settings disabled on the ISP router, it would not work.

 

To get it working, I set my ISP router into bridge mode, exposing the ISP WAN IP to a real router (edgerouter x) to avoid double NAT and set it up as normal from there.

Hi jarch3r,

I'm in the exact situation that you were in.

When you used the edgerouter X were you able to get full 1gbps speeds? I'm only getting like 400 down and 400 up.

It seems like IP Passthrough from the BGW210 is the only option to get letsencrypt working, but then i loose all my speed when I'm under the edgrouter.