1.0 RC4 Apache ProxyPass not working

Questions and bug reports for Beta releases should be posted here.
Forum rules
Help us help you:
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
User avatar
E71
Newbie
Newbie
Posts: 42
Joined: January 13th, 2009, 10:08 pm

1.0 RC4 Apache ProxyPass not working

Post by E71 »

Anyone else having issues with hiding SABnzbd behind web server after upgrading to 1.0 RC4? (I upgraded from 0.7.20 so it could have been betas/RCs in-between.)

SABnzbd only works now in its default http://hostname:port/sabnzbd/ form.

Also, when you restart, it tries to redirect to http://hostname:port/sabnzbd/ instead of http://hostname/your/custom/url.

---------------
CentOS 6.5 / SABnzbd 1.0 RC4 / Apache 2.2.15
Last edited by E71 on March 11th, 2016, 1:12 pm, edited 1 time in total.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: 1.0 RC4 Apache ProxyPass not working

Post by shypike »

Which skin are you using? Glitter, Plush, smpl?
User avatar
E71
Newbie
Newbie
Posts: 42
Joined: January 13th, 2009, 10:08 pm

Re: 1.0 RC4 Apache ProxyPass not working

Post by E71 »

I was using Glitter - Default.

When you browse to the main page via custom url, page source is:

Code: Select all


    
    
    Paused 
    
    - SABnzbd

|||0
sabnzbd.log:

Code: Select all

2016-03-11 12:22:33,572::INFO::[SABnzbd:1243] --------------------------------
2016-03-11 12:22:33,572::INFO::[SABnzbd:1244] SABnzbd.py-1.0.0RC4 (rev=1ba99769794134b18c8416631d51283ac4409b88)
2016-03-11 12:22:33,572::INFO::[SABnzbd:1245] Full executable path = /opt/sabnzbd/SABnzbd.py
2016-03-11 12:22:33,572::INFO::[SABnzbd:1257] Platform = posix
2016-03-11 12:22:33,572::INFO::[SABnzbd:1258] Python-version = 2.6.6 (r266:84292, Jul 23 2015, 15:22:56)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-11)]
2016-03-11 12:22:33,573::INFO::[SABnzbd:1259] Arguments = SABnzbd.py --server 0.0.0.0:8181 -d --config-file /home/newser/.sabnzbd/sabnzbd.ini
2016-03-11 12:22:33,573::INFO::[SABnzbd:1304] Read INI file /home/newser/.sabnzbd/sabnzbd.ini
2016-03-11 12:22:33,593::INFO::[__init__:965] Loading data for rss_data.sab from /home/newser/.sabnzbd/usenet/admin/rss_data.sab
2016-03-11 12:22:33,657::INFO::[__init__:965] Loading data for totals10.sab from /home/newser/.sabnzbd/usenet/admin/totals10.sab
2016-03-11 12:22:33,658::INFO::[postproc:89] Loading postproc queue
2016-03-11 12:22:33,658::INFO::[__init__:965] Loading data for postproc2.sab from /home/newser/.sabnzbd/usenet/admin/postproc2.sab
2016-03-11 12:22:33,659::INFO::[__init__:965] Loading data for queue10.sab from /home/newser/.sabnzbd/usenet/admin/queue10.sab
2016-03-11 12:22:33,660::INFO::[__init__:965] Loading data for watched_data2.sab from /home/newser/.sabnzbd/usenet/admin/watched_data2.sab
2016-03-11 12:22:33,660::INFO::[__init__:965] Loading data for Rating.sab from /home/newser/.sabnzbd/usenet/admin/Rating.sab
2016-03-11 12:22:33,661::INFO::[scheduler:190] Setting schedule for midnight BPS reset
2016-03-11 12:22:33,662::INFO::[downloader:241] Resuming
2016-03-11 12:22:33,662::INFO::[__init__:349] All processes started
2016-03-11 12:22:33,663::INFO::[SABnzbd:355] Web dir is /opt/sabnzbd/interfaces/Glitter
2016-03-11 12:22:33,663::INFO::[SABnzbd:355] Web dir is /opt/sabnzbd/interfaces/smpl
2016-03-11 12:22:33,663::INFO::[SABnzbd:355] Web dir is /opt/sabnzbd/interfaces/Config
2016-03-11 12:22:33,782::INFO::[SABnzbd:483] _yenc module... found!
2016-03-11 12:22:33,782::INFO::[SABnzbd:491] par2 binary... found (/usr/local/bin/par2)
2016-03-11 12:22:33,782::INFO::[SABnzbd:496] par2-classic binary... found (/usr/local/bin/par2)
2016-03-11 12:22:33,783::INFO::[SABnzbd:499] UNRAR binary... found (/usr/bin/unrar)
2016-03-11 12:22:33,783::INFO::[SABnzbd:505] unzip binary... found (/usr/bin/unzip)
2016-03-11 12:22:33,783::INFO::[SABnzbd:511] 7za binary... found (/usr/bin/7za)
2016-03-11 12:22:33,783::INFO::[SABnzbd:518] nice binary... found (/bin/nice)
2016-03-11 12:22:33,783::INFO::[SABnzbd:522] ionice binary... found (/usr/bin/ionice)
2016-03-11 12:22:33,783::INFO::[SABnzbd:527] pyOpenSSL... found (True)
2016-03-11 12:22:33,783::INFO::[SABnzbd:1367] SSL version OpenSSL 1.0.1e-fips 11 Feb 2013
2016-03-11 12:22:33,784::INFO::[SABnzbd:1368] pyOpenSSL version 0.13.1
2016-03-11 12:22:33,784::INFO::[SABnzbd:1369] SSL potentially supported protocols ['SSLv2', 'SSLv23', 'SSLv3', 'TLSv1']
2016-03-11 12:22:33,784::INFO::[SABnzbd:1370] SSL actually supported protocols ['t1', 'v23', 'v3', 'v2']
2016-03-11 12:22:33,787::INFO::[SABnzbd:1516] Starting web-interface on 0.0.0.0:9191
2016-03-11 12:22:33,789::INFO::[_cplogging:216] [11/Mar/2016:12:22:33] ENGINE Bus STARTING
2016-03-11 12:22:33,795::INFO::[_cplogging:216] [11/Mar/2016:12:22:33] ENGINE Started monitor thread '_TimeoutMonitor'.
2016-03-11 12:22:34,019::INFO::[_cplogging:216] [11/Mar/2016:12:22:34] ENGINE Serving on https://0.0.0.0:9191
2016-03-11 12:22:34,121::INFO::[_cplogging:216] [11/Mar/2016:12:22:34] ENGINE Serving on http://0.0.0.0:8181
2016-03-11 12:22:34,121::INFO::[_cplogging:216] [11/Mar/2016:12:22:34] ENGINE Bus STARTED
2016-03-11 12:22:34,121::INFO::[zconfig:64] No Bonjour/ZeroConfig support installed
2016-03-11 12:22:34,376::INFO::[SABnzbd:1588] Starting SABnzbd.py-1.0.0RC4
2016-03-11 12:22:34,378::INFO::[dirscanner:302] Dirscanner starting up
2016-03-11 12:22:34,379::INFO::[urlgrabber:69] URLGrabber starting up
2016-03-11 12:22:48,666::INFO::[rss:570] Starting scheduled RSS read-out for "EXAMPLEFEED"
2016-03-11 12:22:50,931::INFO::[rss:531] Ignoring duplicate job EXAMPLEJOB
2016-03-11 12:23:06,051::INFO::[__init__:941] Saving data for rss_data.sab in /home/newser/.sabnzbd/usenet/admin/rss_data.sab
2016-03-11 12:23:06,105::INFO::[rss:584] Finished scheduled RSS read-outs
Relevant part of httpd.conf:

Code: Select all

<Location /your/custom/url>
        order deny,allow
        deny from all
        allow from all
        ProxyPass http://localhost:8181/sabnzbd
        ProxyPassReverse http://localhost:8181/sabnzbd
</Location>
If you need any other info, let me know.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: 1.0 RC4 Apache ProxyPass not working

Post by shypike »

So it does work when you use the standard name?
If so, we'll leave it at this for the moment.
User avatar
E71
Newbie
Newbie
Posts: 42
Joined: January 13th, 2009, 10:08 pm

Re: 1.0 RC4 Apache ProxyPass not working

Post by E71 »

Yes, it only works if you directly visit http://servername:8181/sabnzbd.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: 1.0 RC4 Apache ProxyPass not working

Post by shypike »

OK, we'll look at this later.
We're still releasing 1.0.0Final this weekend; it's too long overdue.
Can you help us remember by filing an issue on github? https://github.com/sabnzbd/sabnzbd/issues
User avatar
safihre
Administrator
Administrator
Posts: 5365
Joined: April 30th, 2015, 7:35 am
Contact:

Re: 1.0 RC4 Apache ProxyPass not working

Post by safihre »

The part you are seeing is Glitter specific and is this url:
/sabnzbd/queue/
So very weird actually that it chooses to show that one..

I don't know anything about Apache proxies, but maybe change these lines
ProxyPass http://localhost:8181/sabnzbd
ProxyPassReverse http://localhost:8181/sabnzbd
to
ProxyPass http://localhost:8181/sabnzbd/
ProxyPassReverse http://localhost:8181/sabnzbd/
?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
User avatar
E71
Newbie
Newbie
Posts: 42
Joined: January 13th, 2009, 10:08 pm

Re: 1.0 RC4 Apache ProxyPass not working

Post by E71 »

Well, this is embarrassing. I figured out it was my own fault.

Thanks to browser history, years of visiting the /queue/ url instead of the main page, it kinda became second nature and so I totally forgot that ".../queue/" may be specific to the skin I've been using.

Sorry for wasting your time guys and thanks safihre for pointing out the "/queue/" thing.
Post Reply