Ping monitor, fails to punicode decode international domain names like münchen.de #4593

Closed
opened 2026-02-28 04:08:38 -05:00 by deekerman · 2 comments
Owner

Originally created by @iotux on GitHub (Jan 9, 2026).

  • #570 is old and closed, but may be related

🛡️ Security Policy

📝 Description

Adding a ping monitor for "münchen.de" results in the following message

2026-01-09T12:23:06+01:00 [MONITOR] WARN: Monitor #33 'münchen.de': Failing: ping: münchen.de: Parameter string not correctly encoded

👟 Reproduction steps

Adding a Ping monitor with any IDN domain name

👀 Expected behavior

Adding a Ping monitor for a IDN domain should behave equally to any other domain name

😓 Actual Behavior

Image

🐻 Uptime-Kuma Version

Latest

💻 Operating System and Arch

Ubuntu 25.10

🌐 Browser

Any

🖥️ Deployment Environment

  • Runtime Environment:
    • Node.js: Version X.X.X (LTS: Yes/No)
  • Database:
    • SQLite: Embedded
  • Database Storage:
    • Filesystem:
      • Linux: ext4
    • Storage Medium: NVMe
  • Uptime Kuma Setup:
    • Number of monitors: 1

📝 Relevant log output

2026-01-09T12:23:06+01:00 [MONITOR] WARN: Monitor #33 'münchen.de': Failing: ping: münchen.de: Parameter string not correctly encoded
Originally created by @iotux on GitHub (Jan 9, 2026). ### 📑 I have found these related issues/pull requests - #570 is old and closed, but may be related ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Description Adding a ping monitor for "münchen.de" results in the following message ```bash 2026-01-09T12:23:06+01:00 [MONITOR] WARN: Monitor #33 'münchen.de': Failing: ping: münchen.de: Parameter string not correctly encoded ``` ### 👟 Reproduction steps Adding a Ping monitor with any IDN domain name ### 👀 Expected behavior Adding a Ping monitor for a IDN domain should behave equally to any other domain name ### 😓 Actual Behavior <img width="610" height="119" alt="Image" src="https://github.com/user-attachments/assets/d7644bb0-354c-4c7d-92d5-4bd150179cc8" /> ### 🐻 Uptime-Kuma Version Latest ### 💻 Operating System and Arch Ubuntu 25.10 ### 🌐 Browser Any ### 🖥️ Deployment Environment - **Runtime Environment**: - Node.js: Version `X.X.X` (LTS: Yes/No) - **Database**: - SQLite: Embedded - **Database Storage**: - **Filesystem**: - Linux: ext4 - **Storage Medium**: NVMe - **Uptime Kuma Setup**: - Number of monitors: `1` ### 📝 Relevant log output ```bash session 2026-01-09T12:23:06+01:00 [MONITOR] WARN: Monitor #33 'münchen.de': Failing: ping: münchen.de: Parameter string not correctly encoded ```
deekerman 2026-02-28 04:08:38 -05:00
Author
Owner

@CommanderStorm commented on GitHub (Jan 9, 2026):

Latest

Just to make sure, you mean v2? The :latest docker tag is v1

@CommanderStorm commented on GitHub (Jan 9, 2026): > Latest Just to make sure, you mean v2? The :latest docker tag is v1
Author
Owner

@iotux commented on GitHub (Jan 9, 2026):

Latest

Just to make sure, you mean v2? The :latest docker tag is v1

Sorry if I have mixed in docker here.
I don't use docker for this. I am referring to 2.1.0 as latest

@iotux commented on GitHub (Jan 9, 2026): > > Latest > > Just to make sure, you mean v2? The :latest docker tag is v1 Sorry if I have mixed in docker here. I don't use docker for this. I am referring to 2.1.0 as latest
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#4593
No description provided.