malformed HTTP response #55

Closed
opened 2025-12-29 14:23:32 +01:00 by adam · 4 comments
Owner

Originally created by @mrg358 on GitHub (Apr 20, 2025).

This error shows up right after login to Web UI

godoxy           | 04-20 12:13 ERR http proxy error error="net/http: HTTP/1.x transport connection broken: malformed HTTP response \"\\x15\\x03\\x01\\x00\\x02\\x022\\x15\\x03\\x01\\x00\\x02\\x01\\x00\"" url=127.0.0.1:8888/
godoxy           | 04-20 12:13 ERR http proxy error error="remote error: tls: no application protocol" url=127.0.0.1:8888/
Originally created by @mrg358 on GitHub (Apr 20, 2025). This error shows up right after login to Web UI ``` godoxy | 04-20 12:13 ERR http proxy error error="net/http: HTTP/1.x transport connection broken: malformed HTTP response \"\\x15\\x03\\x01\\x00\\x02\\x022\\x15\\x03\\x01\\x00\\x02\\x01\\x00\"" url=127.0.0.1:8888/ godoxy | 04-20 12:13 ERR http proxy error error="remote error: tls: no application protocol" url=127.0.0.1:8888/ ```
adam closed this issue 2025-12-29 14:23:32 +01:00
Author
Owner

@yusing commented on GitHub (Apr 20, 2025):

The sequence \x15\x03\x01 is the start of a TLS record. Do you have other services that is listening https on port 8888?

@yusing commented on GitHub (Apr 20, 2025): The sequence \x15\x03\x01 is the start of a TLS record. Do you have other services that is listening https on port 8888?
Author
Owner

@mrg358 commented on GitHub (Apr 21, 2025):

When I installed godoxy there was another container (stirling-pdf) running on port 8888. So I changed the port of stirling and tried to reinstall godoxy from scratch. The error still persist. Only godoxy running on port 8888.

I tried to change the godoxy port to 8889 in .env with no luck, same error. The error shows up right after login into web-ui.

@mrg358 commented on GitHub (Apr 21, 2025): When I installed godoxy there was another container (stirling-pdf) running on port 8888. So I changed the port of stirling and tried to reinstall godoxy from scratch. The error still persist. Only godoxy running on port 8888. I tried to change the godoxy port to 8889 in .env with no luck, same error. The error shows up right after login into web-ui.
Author
Owner

@mrg358 commented on GitHub (Apr 21, 2025):

So I found the error msg was related to some of the containers running in unhealthy state. After shutting them down the error msg went away.

Considering a docker host running a bunch of services in advance, this error can be pretty common in the future. It would be helpful if the error msg could point directly to to the service causing the problem.

@mrg358 commented on GitHub (Apr 21, 2025): So I found the error msg was related to some of the containers running in unhealthy state. After shutting them down the error msg went away. Considering a docker host running a bunch of services in advance, this error can be pretty common in the future. It would be helpful if the error msg could point directly to to the service causing the problem.
Author
Owner

@yusing commented on GitHub (Apr 21, 2025):

It's suggested to remove the port mapping part from docker compose or map them to a ports to avoid port conflicts:

services:
  app:
    - 80
@yusing commented on GitHub (Apr 21, 2025): It's suggested to remove the port mapping part from docker compose or map them to a ports to avoid port conflicts: ```yaml services: app: - 80 ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/godoxy-yusing#55