Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

ProxyPass configuration

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,280
And the urbackup issue sounds similar, it's not finding an index file to serve. You'll likely have to add the webroot to the "to" directive so it will find the index file if it's installed in a subdirectory.
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,280
If you haven't noticed you've piqued my interest with your Caddy installation. I'm very interested in this after doing some reading.
 

danb35

FreeNAS Wizard
Joined
Aug 16, 2011
Messages
10,790
You'll likely have to add the webroot to the "to" directive so it will find the index file if it's installed in a subdirectory.
The confusing thing is that both Urbackup and SABnzbd+ are installed at the root--the "to" addresses I gave in my example are the addresses I use to access them. In the case of Urbackup, no path is ever added as far as I can see. With SAB, a path is added if I go to pages other than the main page (/config/general, /config/folders, etc.), but not on the main page.

I see enough examples of configuring Apache or nginx to reverse proxy for SABnzbd+ that I'm sure it can be done, and none of them mention any changes to SAB's configuration, so the behavior I'm seeing is somewhat puzzling.

I did get some logging going on caddy, and here's what I'm seeing:
Code:
192.168.1.241 - [20/May/2016:21:16:03 -0400] "GET /urbackup HTTP/1.1" 404 22
192.168.1.241 - [20/May/2016:21:16:52 -0400] "GET /urbackup HTTP/1.1" 404 13
192.168.1.241 - [20/May/2016:21:18:51 -0400] "GET /urbackup/ HTTP/1.1" 404 22
192.168.1.241 - [20/May/2016:21:23:00 -0400] "GET /nzb/ HTTP/1.1" 303 98
192.168.1.241 - [20/May/2016:21:23:32 -0400] "GET /nzb/ HTTP/1.1" 303 98


The "404 13" line results in "404 Not Found" in the browser, while the "404 22" gives "Sorry. File not found."
 

danb35

FreeNAS Wizard
Joined
Aug 16, 2011
Messages
10,790
Just checked in the chat support for Caddy. The DNS challenge for Let's Encrypt isn't supported at this time; the developer says he's working on it for the next version. That's going to mean it won't do SSL for me right now, which is OK since that really isn't a high priority, but it'd be nice to get it working.
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,280
Did you manage to get any further with this?
 

danb35

FreeNAS Wizard
Joined
Aug 16, 2011
Messages
10,790
Top