Outside reproduction fails. http://127.0.0.1:57645/proxy/ not found.

[postbios]

Hi,

On my local LAN everything works perfectly, but when accessing remotely (over the Internet) using either port 58050 (HTTP) or 58051 (HTTPS), BubbleUPnP Server always fails with the following error:

[qtp463215441-166 (166) ] WARNING - 0:02:31.564 - .n : failed to get headers: http://127.0.0.1:57645/proxy/H4sIAAAAAAAA_wXB2w2AIAwAwI1sCS9hG4ES-VAbqESd3rtdhEcESE0ysbTrXJ73i3ZFq-Dmkwf1SR2GdNoOmK3QBcrlmm3yxSqdPRZfQ1qrRo3OoC5hOdj803LCbFkAAAA=.mp4: java.net.ConnectException: Connection refused

Nothing is ever listening on that port (127.0.0.1:57645), and the error happens consistently.
I’ve tested with a clean installation and several different system/network configurations (HTTP, HTTPS, behind Apache reverse proxy, direct access, etc.), and it always fails in the same way.

Streaming works, audio works, but the video metadata (ffprobe headers) always fails because of this “local loopback proxy” connection attempt.

Could you please confirm if this is a known issue or regression in recent builds?
Is there any way to disable or redirect that internal “127.0.0.1:xxxx/proxy” call?

Thanks!

[Bubblesoft]

Android BubbleUPnP own media server has a http server that always listen on 127.0.0.1:57645 so that ConnectException is unusual.

I could verify that the encoded part after proxy/ point to a stream URL managed by 'BubbleUPnP Server' (its hostname starts with "bit").

No idea why Android BubbleUPnP cannot connect to 127.0.0.1:57645. Do you have a VPN app that could interfere with networking ?

Other that that, an intermediate "proxy" URL is used to play the stream because you enabled More > Settings > Internet access with BubbleUPnP Server > [pick remote network] > https streaming. Disable that settings and this will make Android BubbleUPnP access the BubbleUPnP Server stream directly (no proxy).

The reason there is this intermediate proxying when "https streaming" is enabled is to make it look like a http stream to the playing client, which can be an external renderer that has issue with https.

[postbios]

Hi Bubblesoft,

Thanks for your quick response. I've run some additional tests and have managed to narrow down the issue to a specific scenario: remote HTTPS access using a custom SSL certificate.

Here’s a summary of my findings:

• Working configurations:

  • Remote HTTP access (port 58050): Everything works perfectly.

  • Local access: Both HTTP and HTTPS (using my domain linked to internal IPs) function as expected.

• Consistently failing configuration:

  • Remote HTTPS access (port 58051): The Connection refused error on 127.0.0.1:57645 reliably reproduces. I’ve confirmed this by disabling all networking on my end, including virtual machine networks, and by removing all iptables rules. The problem persists only in this specific case.

While using the HTTP connection is a perfectly good workaround for me, the error with the HTTPS configuration is an interesting edge case. I still don't see anything listening on port 57645 when the error occurs, which is unusual since, as you mentioned, the server should be.

If you can't reproduce this issue on your end, please feel free to ignore it completely. The HTTP connection is a perfectly acceptable solution for my needs.

Thanks for your time and for the excellent work on the software.

[Bubblesoft]

Hi,

Thank you the additional details.

Does that "failed to get headers" error you mentioned in first post  appear in 'BubbleUPnP Server' log files (BubbleUPnPServer.log.0) or in Android BubbleUPnP app log files ?

My previous message was assuming the latter.