Setting up Line Messenger (Notification) Error 400 #555

Closed
opened 2026-02-28 01:50:27 -05:00 by deekerman · 5 comments
Owner

Originally created by @adamh2021 on GitHub (Nov 12, 2021).

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

When attempting to setup Line Messenger, I have been receiving the following error:

Error: Error: Request failed with status code 400 {"message":"The property, 'to', in the request body is invalid (line:-, column:-)"}

I have check the API setup and that's correct. Anyone else come across this issue?

🐻 Uptime-Kuma Version

1.10.2

💻 Operating System and Arch

Ubuntu 20.04

🌐 Browser

Chrome

🐋 Docker Version

No response

🟩 NodeJS Version

No response

Originally created by @adamh2021 on GitHub (Nov 12, 2021). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem When attempting to setup Line Messenger, I have been receiving the following error: `Error: Error: Request failed with status code 400 {"message":"The property, 'to', in the request body is invalid (line:-, column:-)"}` I have check the API setup and that's correct. Anyone else come across this issue? ### 🐻 Uptime-Kuma Version 1.10.2 ### 💻 Operating System and Arch Ubuntu 20.04 ### 🌐 Browser Chrome ### 🐋 Docker Version _No response_ ### 🟩 NodeJS Version _No response_
deekerman 2026-02-28 01:50:27 -05:00
  • closed this issue
  • added the
    Stale
    help
    labels
Author
Owner

@github-actions[bot] commented on GitHub (Sep 23, 2022):

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

@github-actions[bot] commented on GitHub (Sep 23, 2022): We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.
Author
Owner

@github-actions[bot] commented on GitHub (Sep 26, 2022):

This issue was closed because it has been stalled for 2 days with no activity.

@github-actions[bot] commented on GitHub (Sep 26, 2022): This issue was closed because it has been stalled for 2 days with no activity.
Author
Owner

@suminb commented on GitHub (Nov 8, 2023):

I'm having the same issue. Any progress on this?

@suminb commented on GitHub (Nov 8, 2023): I'm having the same issue. Any progress on this?
Author
Owner

@CommanderStorm commented on GitHub (Nov 8, 2023):

No, there has not been a PR to adress any defects in the line messanger or its documentation.
I don't have this messanger set up => cannot currently test it
From the error message, it seems like your lineUserID is invalid

See our contribution guide here: github.com/louislam/uptime-kuma@5b6522a54e/CONTRIBUTING.md

@Ponkhy this notification provider was introduced by you. This has now moved to https://github.com/louislam/uptime-kuma/blob/master/server/notification-providers/line.js
Do you have any clues why this is failing?

@CommanderStorm commented on GitHub (Nov 8, 2023): No, there has not been a PR to adress any defects in the line messanger or its documentation. I don't have this messanger set up => cannot currently test it From the error message, it seems like your `lineUserID` is invalid See our contribution guide here: https://github.com/louislam/uptime-kuma/blob/5b6522a54edad9737fccf195f9eaa25c6fb9d0f6/CONTRIBUTING.md @Ponkhy this notification provider [was introduced by you](https://github.com/louislam/uptime-kuma/pull/227). This has now moved to https://github.com/louislam/uptime-kuma/blob/master/server/notification-providers/line.js Do you have any clues why this is failing?
Author
Owner

@chakflying commented on GitHub (Nov 8, 2023):

  • Looks like an outage was reported recently for the Line API (source)
  • The to property is used to set the recipient of the message. This property is set by the lineUserID of the notification configuration. Maybe you can check Line's API documentation to see if you have set the value correctly.
@chakflying commented on GitHub (Nov 8, 2023): - Looks like an outage was reported recently for the Line API ([source](https://api.line-status.info/)) - The `to` property is used to set the recipient of the message. This property is set by the `lineUserID` of the notification configuration. Maybe you can check Line's [API documentation](https://developers.line.biz/en/reference/messaging-api/#send-push-message-request-body) to see if you have set the value correctly.
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#555
No description provided.