starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

HP Color LazerJet MFP M277dw HTTP Monitor Not Working #4316

New issue

Open

opened 2026-02-28 03:58:08 -05:00 by deekerman · 11 comments

deekerman commented

2026-02-28 03:58:08 -05:00

Owner

Originally created by @ucdscott on GitHub (Sep 28, 2025).

Unable to find any issues related to HP printers.

🛡️ Security Policy

I have read and agree to Uptime Kuma's Security Policy.

📝 Description

http://192.168.0.206/

Must be a bug?

👟 Reproduction steps

http://192.168.0.206/

👀 Expected behavior

200 - OK

😓 Actual Behavior

response timeout: incomplete response within a interval

🐻 Uptime-Kuma Version

1.23.16

💻 Operating System and Arch

Synology DSM 7, Container Manager

🌐 Browser

Firefox 143.0.1 (64-bit)

🖥️ Deployment Environment

Runtime Environment:
- Docker: Version Synology Container Manager
Uptime Kuma Setup:
- Number of monitors: 15ish

📝 Relevant log output

response timeout: incomplete response within a interval

Originally created by @ucdscott on GitHub (Sep 28, 2025). ### 📑 I have found these related issues/pull requests Unable to find any issues related to HP printers. ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Description http://192.168.0.206/ <img height="400" alt="Image" src="https://github.com/user-attachments/assets/b087d479-e060-4f79-90d0-6d4c9693244f" /><img width="40%" height="471" alt="Image" src="https://github.com/user-attachments/assets/413e7637-c2e6-45b2-a25b-a8fef935bbd9" /><img width="40%" height="419" alt="Image" src="https://github.com/user-attachments/assets/45571cc2-3a28-41b7-9abd-9f4cd9fc3e01" /> Must be a bug? ### 👟 Reproduction steps http://192.168.0.206/ ### 👀 Expected behavior 200 - OK ### 😓 Actual Behavior response timeout: incomplete response within a interval ### 🐻 Uptime-Kuma Version 1.23.16 ### 💻 Operating System and Arch Synology DSM 7, Container Manager ### 🌐 Browser Firefox 143.0.1 (64-bit) ### 🖥️ Deployment Environment - **Runtime Environment**: - Docker: Version Synology Container Manager - **Uptime Kuma Setup**: - Number of monitors: `15ish` ### 📝 Relevant log output ```bash session response timeout: incomplete response within a interval ```

deekerman added the

question

help

labels

2026-02-28 03:58:08 -05:00

deekerman commented

2026-02-28 03:58:10 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Sep 28, 2025):

Please follow our troubleshooting instructions:
https://github.com/louislam/uptime-kuma/wiki/Troubleshooting

Also make sure that you and uptime kuma are on the same network.
http://192.168.0.206/ is private, meaning it caonnot be routed via the internet

@CommanderStorm commented on GitHub (Sep 28, 2025): Please follow our troubleshooting instructions: https://github.com/louislam/uptime-kuma/wiki/Troubleshooting Also make sure that you and uptime kuma are on the same network. http://192.168.0.206/ is private, meaning it caonnot be routed via the internet

deekerman commented

2026-02-28 03:58:13 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 19, 2025):

We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

@github-actions[bot] commented on GitHub (Dec 19, 2025): We are clearing up our old `help`-issues and your issue has been open for 60 days with no activity. If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

deekerman commented

2026-02-28 03:58:13 -05:00

Author

Owner

@ucdscott commented on GitHub (Dec 21, 2025):

This is not a networking issue. All other servers are reporting uptime status correctly:

@ucdscott commented on GitHub (Dec 21, 2025): This is not a networking issue. All other servers are reporting uptime status correctly: <img width="35%" height="671" alt="Image" src="https://github.com/user-attachments/assets/d9f87642-ca0d-447a-9704-92109c7efc9a" /><img width="30%" height="761" alt="Image" src="https://github.com/user-attachments/assets/27137357-c334-45e1-aa65-df30235cbfd6" /><img width="35%" height="508" alt="Image" src="https://github.com/user-attachments/assets/d473ce64-66e3-49fc-bc3a-1d60104c989e" /> <img width="808" height="89" alt="Image" src="https://github.com/user-attachments/assets/6e64af36-4b18-4a03-9c35-f1f8005300f2" />

deekerman commented

2026-02-28 03:58:13 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 22, 2025):

Have you followed our troubleshooting steps?

@CommanderStorm commented on GitHub (Dec 22, 2025): Have you followed our troubleshooting steps?

deekerman commented

2026-02-28 03:58:13 -05:00

Author

Owner

@ucdscott commented on GitHub (Dec 22, 2025):

Yes, "This is not a networking issue."

root@15f863c8cabd:/app# curl http://192.168.0.206

root@15f863c8cabd:/app# curl -k https://192.168.0.206

@ucdscott commented on GitHub (Dec 22, 2025): Yes, "This is not a networking issue." root@15f863c8cabd:/app# curl http://192.168.0.206 <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> <title>HP Color LaserJet MFP M277dw   192.168.0.206</title> root@15f863c8cabd:/app# curl -k https://192.168.0.206 <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> <title>HP Color LaserJet MFP M277dw   192.168.0.206</title>

deekerman commented

2026-02-28 03:58:13 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 22, 2025):

It seems above screenshot that you resolved the issue. At least it is not showing the incomplete response.

If this is a sporadic issue, try troubleshooting this a bit more.
Not sending the whole thing over the wire is a real issue. I don't see a bug in uptime kuma there.
Debugging networking issues over GitHub is extremely hard.

@CommanderStorm commented on GitHub (Dec 22, 2025): It seems above screenshot that you resolved the issue. At least it is not showing the incomplete response. If this is a sporadic issue, try troubleshooting this a bit more. Not sending the whole thing over the wire is a real issue. I don't see a bug in uptime kuma there. Debugging networking issues over GitHub is extremely hard.

deekerman commented

2026-02-28 03:58:13 -05:00

Author

Owner

@ucdscott commented on GitHub (Dec 22, 2025):

What? How is this resolved?

What does "Not sending the whole thing over the wire" mean?

How do you propose I "try troubleshooting this a bit more?"

Again, this is not a networking issue. The Uptime Kuma container can reach the HTTP endpoint just fine, yet Uptime Kuma still reports Status = Down.

What information do you need from me that I have not provided?

@ucdscott commented on GitHub (Dec 22, 2025): What? How is this resolved? What does "Not sending the whole thing over the wire" mean? How do you propose I "try troubleshooting this a bit more?" Again, this is not a networking issue. The Uptime Kuma container can reach the HTTP endpoint just fine, yet Uptime Kuma still reports Status = Down. What information do you need from me that I have not provided? <img width="1195" height="947" alt="Image" src="https://github.com/user-attachments/assets/e914ea6e-0747-4c56-8697-20833599ef63" />

deekerman commented

2026-02-28 03:58:13 -05:00

Author

Owner

@louislam commented on GitHub (Dec 22, 2025):

I guess the web interface is not completely following web standard. They probably write their web server to serve the interface from scratch. They may be fine on browsers, but not other http clients.

I think you should try other paths like http://192.168.0.206/jquery.js

@louislam commented on GitHub (Dec 22, 2025): I guess the web interface is not completely following web standard. They probably write their web server to serve the interface from scratch. They may be fine on browsers, but not other http clients. I think you should try other paths like http://192.168.0.206/jquery.js

deekerman commented

2026-02-28 03:58:13 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 22, 2025):

Tip

First of all, let’s keep the conversation constructive and respectful.
I understand that this situation is frustrating, and I appreciate your patience.

Please keep in mind that this is an open-source project maintained by volunteers in their free time.
I don’t have visibility into your setup unless you share it with me.

If you’d like help, providing detailed and relevant information about the issue (such as debug logs, your exact configuration, and steps to reproduce) will make it much easier for me or others to assist you.

It seems above screenshot that you resolved the issue. At least it is not showing the incomplete response.

What? How is this resolved?

Here is the screenshot I am refering to

How do you propose I "try troubleshooting this a bit more?"

I would try curl -v, then wireshark to look at what is incomplete about your servers response.

Again, this is not a networking issue.
The Uptime Kuma container can reach the HTTP endpoint just fine, yet Uptime Kuma still reports Status = Down.

From the information shared so far, the HTTP response itself appears to be incomplete or malformed. That usually points to a server-side issue rather than a problem inside Uptime Kuma.

Unfortunately, without more detailed diagnostics it’s difficult to narrow down the exact cause. To better understand what’s happening on the wire, additional debug information would be very helpful.

There are a few node flags surrounding relaxing the header handling, but I would recomend to first see what the issue is before we go down that path.

@CommanderStorm commented on GitHub (Dec 22, 2025): > [!TIP] > First of all, let’s keep the conversation constructive and respectful. > I understand that this situation is frustrating, and I appreciate your patience. > > Please keep in mind that this is an open-source project maintained by volunteers in their free time. > I don’t have visibility into your setup unless you share it with me. > > If you’d like help, providing detailed and relevant information about the issue (such as debug logs, your exact configuration, and steps to reproduce) will make it much easier for me or others to assist you. > > It seems above screenshot that you resolved the issue. At least it is not showing the incomplete response. > > What? How is this resolved? Here is the screenshot I am refering to <img width="809" height="342" alt="Image" src="https://github.com/user-attachments/assets/9f0d0cbb-2a44-4699-b622-3fcf99fb89e3" /> > How do you propose I "try troubleshooting this a bit more?" I would try `curl -v`, then wireshark to look at what is incomplete about your servers response. > Again, this is not a networking issue. > The Uptime Kuma container can reach the HTTP endpoint just fine, yet Uptime Kuma still reports Status = Down. From the information shared so far, the HTTP response itself appears to be incomplete or malformed. That usually points to a server-side issue rather than a problem inside Uptime Kuma. Unfortunately, without more detailed diagnostics it’s difficult to narrow down the exact cause. To better understand what’s happening on the wire, additional debug information would be very helpful. There are a few `node` flags surrounding relaxing the header handling, but I would recomend to first see what the issue is before we go down that path.

deekerman commented

2026-02-28 03:58:13 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 21, 2026):

We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

@github-actions[bot] commented on GitHub (Feb 21, 2026): We are clearing up our old `help`-issues and your issue has been open for 60 days with no activity. If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

deekerman commented

2026-02-28 03:58:13 -05:00

Author

Owner

@ucdscott commented on GitHub (Feb 25, 2026):

HP Color LaserJet (HTTP 80).zip

Two different pcapng files attached (inside of zip file). One using Firefox as the client. The other using curl.

@ucdscott commented on GitHub (Feb 25, 2026): [HP Color LaserJet (HTTP 80).zip](https://github.com/user-attachments/files/25537015/HP.Color.LaserJet.HTTP.80.zip) Two different pcapng files attached (inside of zip file). One using Firefox as the client. The other using curl.