Has anyone gotten the new Reverse Proxy to work?

[Nazar78]

Hi,
Has anyone had success with nextcloud on docker ?

When at home, I can use https://mydomain.myasustor.com:32681 to connect to my nextcloud instance at http://192.168.1.200:32680
Reverse proxy seems to be working.

When on another network, the same request times out. I suspect it has something to do with nextcloud config / https but I can't find any solution anywhere. Could anyone help ?
Thanks !

Is the port 32681 open in your router? Else it will usually result in connection refused. Can you connect to ADM while using external network? Timeout usually means your ddns is not working properly. Try ping the ddns see if it resolves to your public IP even though if the ping timed out it's just to ensure your ddns points correctly to your public IP.

For nextcloud, point the reverse proxy to the http port of the app. You can however use https on the reverse proxy. I'm not sure of your config but take a look at the docs here https://docs.nextcloud.com/server/lates ... ation.html

[Bennas]

Is the port 32681 open in your router?

Yes, it does show in the UPnP port list (for TCP)

Can you connect to ADM while using external network? Timeout usually means your ddns is not working properly. Try ping the ddns see if it resolves to your public IP even though if the ping timed out it's just to ensure your ddns points correctly to your public IP.

If I use mydyndns.myasustor.com it does show ADM login page.

For nextcloud, point the reverse proxy to the http port of the app. You can however use https on the reverse proxy. I'm not sure of your config but take a look at the docs here https://docs.nextcloud.com/server/lates ... ation.html

I think I'm Ok for the reverse proxy settings. You can find a screenshot of the settings in the attachment.

Thanks again for your help !

[ilike2burnthing]

Original issue fixed in 3.5.4.RE11!

Socket upgrade thingy for Portainer still has to be done manually though. Will send them a message, see if it's on the cards.

[The PyroPath]

Would this function also work for a Transmission webui reverse proxy? I'm running Haugene-transmission-openvpn through portainer, but unable to connect to the webui over WAN. It says with very few words to set up a reverse proxy, but my knowledge about portainer is so small, I don't know where to start with that... And if it would work, could I get a little help on how to set it up? Because I've had a look and most fields are....well confusing without examples or helpfile...

[ilike2burnthing]

Currently using ADM reverse proxy with the same Transmission image. Nothing special to set up in Portainer, just both ADM reverse proxy paths set to:

Code: Select all

/transmission/

The URL used to access it should end in /
https://AsustorID.myasustor.com/transmission/web/

[The PyroPath]

Currently using ADM reverse proxy with the same Transmission image. Nothing special to set up in Portainer, just both ADM reverse proxy paths set to:

Code: Select all

/transmission/

The URL used to access it should end in /
https://AsustorID.myasustor.com/transmission/web/

This completely boggles my mind. Didn't work at first, so I threw out all ports from the router, ez router etc. Started with resetting NAS and router. Set up https and different ports to use 19091 on proxy and linked to 9092 over http on the local Lan IP. Then it worked. Had to restart the NAS for something else and after that I can't access it from outside anymore. Tried retaking all previous steps, but it just doesn't go back to working.

[The PyroPath]

OK, this is driving me nuts... This is what I did:

Code: Select all

[b]Proxy domain[/b]
Title: trans
Protocol: HTTPS
Domain: [asustor ID].myasustor.com
Port#: 19091
Network interface: LAN 1 / [LOCAL NAS IP]
Path: /transmission/web/
Also enable EZ-Connect port forwarding: Checked

[b]Rule[/b]
Name: trans RP
Protocol: HTTP
Hostname: [LOCAL NAS IP]
Port#: 9091
Path: /transmission/web/
URL redirection: [Remains blank]

Click Test connection... and http://[NAS LOCAL IP]:9091/transmission/web/ opens and everything works. So I click Next.

Now when I open https://[asustor ID].myasustor.com:19091/transmission/web/ the web interface loads but all elements say (Loading...) in Transmission Web Control. All buttons are there, but the torrents aren't there and neither is the data... it's almost like it loads a 2nd instance of the page, but can't connect to the server. When I switch to the classic lay out of the original page lay out it says:

Code: Select all

[b]Connection Failed[/b]

Could not connect to the server. You may need to reload the page to reconnect.
[Dismiss button]  [Details button]

When I push the details button it shows:

Code: Select all

404 Not Found

404 Not Found
nginx

Really scratching my head...

[ilike2burnthing]

Try just /transmission/ instead of /transmission/web/.

Add both ports to port forwarding on your router.

[The PyroPath]

Try just /transmission/ instead of /transmission/web/.

Add both ports to port forwarding on your router.

Uhm, it's now working again, but I don't know why...I just don't understand why it now works though. Because I just tried every and all permutations of the Path (both proxy domain and proxy rule) I could think off, and none worked, but all had a separate type of response and failed and I wanted to do it again and document the responses, but at the first try it worked...

Prerequisite: Locally the web UI is reached by opening the browser and going to https://192.168.0.x:9091/tranmission/web/ and Port forwarding set both manually and trough EZ-router. Don't know if it matters, but since it's working now, I'm reluctant to try

What works right at this moment for the reverse proxy is is the following:

Code: Select all

Prerequisite: Locally the web UI is reached by opening the browser and going to https://192.168.0.x:9091/tranmission/web/
Port forwarding set both manually and trough EZ-router. Don't know if it matters, but since it's working now, I'm reluctant to try ;-)

For Proxy domain:
Title: trans
Protocol: HTTPS
Domain: [asustor ID].myasustor.com
Port#: 19091
Network interface: LAN 1 / [LOCAL NAS IP]
Path: /  (yes, just a plain old slash...)
Also enable EZ-Connect port forwarding: Checked

For Proxy Rule:
Name: trans RP
Protocol: HTTP
Hostname: [LOCAL NAS IP]
Port#: 9091
Path: / ( Yes, again a plain old slash)
URL redirection: [Remains blank]

When I now open the browser and go to https://[Asustor ID].myasustor.com:19091/transmission/web/ the page opens fine and with all elements...

[ilike2burnthing]

Huh, strange. Well hey, whatever works