Hi
This guide has worked perfectly.
I've set up reverseproxy for all my services however does anyone know how to setup reverse proxy for filestation/musicstation etc?
The reason i want to do to this is because i have setup portforwarding to allow access to services but do not want to point an open port directly to my NAS QTS dashboard
For example if the NAS https LAN login address is 192.1.1.1:1234 then how would i setup a reverse proxy pointing to 192.1.1.1:1234/filestation
Ive tried using the below but it does not work
<Location /filestation>
Order deny,allow
ProxyPass http://127.0.0.1:1234/filestation
ProxyPassReverse http://127.0.0.1:1234/filestation
</Location>
[HOW-TO] QNAP Apache Reverse Proxy with SSL using Let's Encrypt (for apps like SickRage, Couchpotato, NZBGet, Sonarr)
-
- Getting the hang of things
- Posts: 74
- Joined: Sun Jun 21, 2009 4:31 pm
-
- Starting out
- Posts: 17
- Joined: Wed Aug 03, 2016 3:59 am
- Location: Ireland
Re: [HOW-TO] QNAP Apache Reverse Proxy with SSL using Let's Encrypt (for apps like SickRage, Couchpotato, NZBGet, Sonarr
Does anyone know how can I undo this tutorial? I've tried resetting my webserver to factory settings and nothing works.
I followed it and now I can access any of my docker apps.
Before trying this tutorial I had a number of subdomains set up and reverse-proxied to load the correct app. e.g. HTTP://sabnzbd.mydomain.com but after the tutorial, everything is broken.
[UPDATE]
Go to: CP > Certificate & Private Key
User the reset option.
I also hit: CP > Applications > Web Server > Restore
and I have my system back to its original working setup.
I followed it and now I can access any of my docker apps.
Before trying this tutorial I had a number of subdomains set up and reverse-proxied to load the correct app. e.g. HTTP://sabnzbd.mydomain.com but after the tutorial, everything is broken.
[UPDATE]
Go to: CP > Certificate & Private Key
User the reset option.
I also hit: CP > Applications > Web Server > Restore
and I have my system back to its original working setup.
-
- New here
- Posts: 8
- Joined: Fri Apr 17, 2015 9:30 am
Re: [HOW-TO] QNAP Apache Reverse Proxy with SSL using Let's Encrypt (for apps like SickRage, Couchpotato, NZBGet, Sonarr
i can't get this to work but I assume because my source is an https not http.
-
- Starting out
- Posts: 13
- Joined: Thu Apr 23, 2015 2:15 pm
Re: [HOW-TO] QNAP Apache Reverse Proxy with SSL using Let's Encrypt (for apps like SickRage, Couchpotato, NZBGet, Sonarr
Hello, need some help please. This was working perfectly until yeterday when I changed transmission with qbittorrent. Once I added it to the customized.conf it did not load, connection refused error. Now, all my reversed proxied application have the same issue, connection refused. I even copied the backup back and same issue. What could've gone wrong?
Thank you!
Thank you!
- oyvindo
- Experience counts
- Posts: 1399
- Joined: Tue May 19, 2009 2:08 am
- Location: Norway, Oslo
Re: [HOW-TO] QNAP Apache Reverse Proxy with SSL using Let's Encrypt (for apps like SickRage, Couchpotato, NZBGet, Sonarr
First check that your Apache.conf file has an include statement at the end to include your customized.conf file.
Then remember that each time you make a change to your customized.conf, you must restart Apache for the change to take effect.
On most QNAP NAS you can do that by the following command:
/usr/local/apache/bin/apachectl restart
Then remember that each time you make a change to your customized.conf, you must restart Apache for the change to take effect.
On most QNAP NAS you can do that by the following command:
/usr/local/apache/bin/apachectl restart
-
- Starting out
- Posts: 13
- Joined: Thu Apr 23, 2015 2:15 pm
Re: [HOW-TO] QNAP Apache Reverse Proxy with SSL using Let's Encrypt (for apps like SickRage, Couchpotato, NZBGet, Sonarr
Yes it is included, I also restarted apache several time, even restarted the NAS. But I used the command /etc/init.d/Qthttpd.sh restart .. should be the same. I tried now installing an nginx container, disabled the Webserver from Qnap, but I still receive the same error...
LE: Nvm, the nginx part was an error from my side
LE: Nvm, the nginx part was an error from my side