2015-08-17, 22:57
I'm having a strange issue where no matter what external link I use or internal link, HTPC-Manager grabs it and then tries to connect to http://127.0.0.1:8085/htpc/auth/login. What makes this even more odd is that I specifically have it configured to use http://192.168.1.100:8085/htpc, when I start HTPC manager it says "you can connect to HTPC-Manager by accessing http://127.0.0.1:8085" even when I specify an address to listen, I've always assumed that this was just a coding error now I'm starting to think differently.
As seen above, I'm using Nginx on FreeBSD 9.3 to hide all my usenet related apps behind a reverse proxy, with HTPC-Manager being the root page. I had this working before but I've been setting up so many different things, something must've changed because it kept doing this, after pulling my hair out for a few hours trying to figure out WTF the problem was I deleted the jail and started over, which included cloning a new copy of HTPC-Manager since it was crashing due to problems with my SSL config (I'm skipping SSL for now). It's back to doing it again and I have no idea what the problem is since I'm relatively new to Nginx and self hosting.
There are no errors in my Nginx logs relating to this, this is the only thing in my access log: [IP Address] - - [17/Aug/2015:14:59:57 -0400] "GET / HTTP/1.1" 302 108 "-" "Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:39.0) Gecko/20100101 Firefox/39.0"
Here's my HTPC-Manager log, which doesn't tell much..
Here's the relevant section of my nginx.conf
As seen above, I'm using Nginx on FreeBSD 9.3 to hide all my usenet related apps behind a reverse proxy, with HTPC-Manager being the root page. I had this working before but I've been setting up so many different things, something must've changed because it kept doing this, after pulling my hair out for a few hours trying to figure out WTF the problem was I deleted the jail and started over, which included cloning a new copy of HTPC-Manager since it was crashing due to problems with my SSL config (I'm skipping SSL for now). It's back to doing it again and I have no idea what the problem is since I'm relatively new to Nginx and self hosting.
There are no errors in my Nginx logs relating to this, this is the only thing in my access log: [IP Address] - - [17/Aug/2015:14:59:57 -0400] "GET / HTTP/1.1" 302 108 "-" "Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:39.0) Gecko/20100101 Firefox/39.0"
Here's my HTPC-Manager log, which doesn't tell much..
Code:
2015-08-15 19:39:12 :: root :: INFO :: Welcome to Hellowlol's HTPC Manager fork
2015-08-15 19:39:12 :: root :: INFO :: Loglevel set to info
2015-08-15 19:39:12 :: htpc.updater :: INFO :: Using GitUpdater engine
2015-08-15 19:39:13 :: apscheduler.scheduler :: INFO :: Added job "Updater.update_needed" to job store "default"
2015-08-15 19:39:13 :: modules.kodi :: WARNING :: No configured kodi-Servers.
2015-08-15 19:39:13 :: modules.newznab :: WARNING :: No configured Indexers.
2015-08-15 19:39:13 :: modules.stats :: ERROR :: 'FreeBSD'
2015-08-15 19:39:13 :: htpc.server :: INFO :: Starting up webserver
2015-08-15 19:39:13 :: cherrypy.error :: INFO :: [15/Aug/2015:19:39:13] ENGINE Listening for SIGHUP.
2015-08-15 19:39:13 :: cherrypy.error :: INFO :: [15/Aug/2015:19:39:13] ENGINE Listening for SIGTERM.
2015-08-15 19:39:13 :: cherrypy.error :: INFO :: [15/Aug/2015:19:39:13] ENGINE Listening for SIGUSR1.
2015-08-15 19:39:13 :: cherrypy.error :: INFO :: [15/Aug/2015:19:39:13] ENGINE Bus STARTING
2015-08-15 19:39:13 :: cherrypy.error :: WARNING :: [15/Aug/2015:19:39:13] ENGINE There are [<_MainThread(MainThread, started 34389128192)>, <Thread(APScheduler, started daemon 34512749568)>] active threads. Daemonizing now may cause strange failures.
2015-08-15 19:39:13 :: cherrypy.error :: INFO :: [15/Aug/2015:19:39:13] ENGINE Forking once.
2015-08-15 19:39:13 :: cherrypy.error :: INFO :: [15/Aug/2015:19:39:13] ENGINE Forking twice.
2015-08-15 19:39:13 :: cherrypy.error :: INFO :: [15/Aug/2015:19:39:13] ENGINE Daemonized to PID: 8128
2015-08-15 19:39:13 :: cherrypy.error :: INFO :: [15/Aug/2015:19:39:13] ENGINE Started monitor thread '_TimeoutMonitor'.
2015-08-15 19:39:13 :: cherrypy.error :: INFO :: [15/Aug/2015:19:39:13] ENGINE PID 8128 written to '/var/run/htpc-manager/htpc-manager.pid'.
2015-08-15 19:39:13 :: cherrypy.error :: INFO :: [15/Aug/2015:19:39:13] ENGINE Serving on 192.168.1.100:8085
2015-08-15 19:39:13 :: cherrypy.error :: INFO :: [15/Aug/2015:19:39:13] ENGINE Bus STARTED
2015-08-15 22:26:27 :: cherrypy.error :: INFO :: [15/Aug/2015:22:26:27] ENGINE Started monitor thread 'Session cleanup'.
Here's the relevant section of my nginx.conf
Code:
server {
listen 192.168.1.103:80 default_server;
server_name mysite.us, femp;
error_log logs/error/reverse-proxy.log info;
access_log logs/access/reverse-proxy.log;
location / {
proxy_pass http://192.168.1.100:8085/htpc;
}