Can't proxy connect through xlights to Alpha Pix 4, getting 404 error after pw

[paddy2123]

I am getting a 404 error when opening Alpha Pix 4 from FPP through proxy. I can ping the Alpha pix from FPP. I can get to the login screen of the Alpha Pix controller through the proxy. When I login I get a 404 and the proxy url is missing. Seems like FPP is not passing the right URL back to the browser?

Steps to get 404 error:
From xlights: Open Alpha Pix 4
Browser opens and shows login screen URL: http://192.168.1.29/proxy/192.168.2.125/
enter default password, click login


URL: http://192.168.1.29/UserLogin
browser:
Not Found
The requested URL was not found on this server.

Apache/2.4.56 (Raspbian) Server at 192.168.1.29 Port 80

FPP: V7.4

[JonD]

Guessing FPP is IP 192.168.1.29 and Alpha Pix is 192.168.2.125

http://192.168.1.29/proxy/192.168.2.125/  (Missing "/UserLogin" redirect)

http://192.168.1.29/UserLogin (Missing proxy information and does not appear to be creating the link correctly)

I have seen this with other controller models.  I suspect it will need to be fixed by a developer as the proxy link does not appear to be correct.  As a workaround you might be able to try the below link and see if it works. 

http://192.168.1.29/proxy/192.168.2.125/UserLogin

Make sure the URL starts with the FPP Proxy http://192.168.1.29/proxy/ in the front, and ends with the controllers ip and link at the end. 192.168.2.125/UserLogin

[CaptainMurdoch]

Some controllers don't handle working through this type of proxy correctly due to their use of absolute instead of relative URLs.  If the controller redirects to "/UserLogin" instead of just "UserLogin" then the proxy/IP_ADDRESS gets stripped from the URL and things break.  In FPP, we went through and tried to make sure that all FPP URLs are proxy-friendly, but some controllers still aren't.

[JonD]

Some controllers don't handle working through this type of proxy correctly due to their use of absolute instead of relative URLs.

The Falcon v4 series had similar issues with the new monitor and visualizer tabs, and it seems like it required some changes to both the Falcon firmware and FPP software to resolve.  However in that case, if you manually entered a custom made URL it would still open the page.  You could not click on the Falcon tab, but you could manually make your own link to get there.  It still might be worth a shot to try it manually, but Chris is absolutely correct, that not every controller supports proxy.

[jnealand]

My very old F16v2b also does not like the proxy for the "Open Proxy" but it seems to work fine on setting up the configs.  Clicking it will take you to the controller but then you can not get thru and menu item line "string ports"