Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No Notifications - Error Connect ENETUNREACH #2189

Closed
2 tasks done
emanueltilly opened this issue Oct 7, 2022 · 6 comments
Closed
2 tasks done

No Notifications - Error Connect ENETUNREACH #2189

emanueltilly opened this issue Oct 7, 2022 · 6 comments

Comments

@emanueltilly
Copy link

emanueltilly commented Oct 7, 2022

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

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

I can not setup any notification services.
Whenever i test the new notification services I have configured (Tried Google Chat, Pushover, Pushbullet) I get error "Error: Error: connect ENETUNREACH" followed by a IPV6 address. The host has internet access and I can successfully resolve and ping external websites.

🐻 Uptime-Kuma Version

1.18.3

💻 Operating System and Arch

Raspian 11 Bullseye

🌐 Browser

Google Chrome 105.0.5195.125

🐋 Docker Version

N/A

🟩 NodeJS Version

18.10.0

@louislam
Copy link
Owner

louislam commented Oct 7, 2022

Still related to your network.

If your network supports IPv6, double check your IPv6 connection on your Pi.
If it is not supported, check why your DNS server gave you IPv6 addresses instead of IPv4.

@emanueltilly
Copy link
Author

Thank you for the quick reply.
I disabled Ipv6 on the host and now there seems to be another error:
"Error: cacheableLookup ENOTFOUND chat.googleapis.com".
I have tried pinging chat.googleapis.com from the host and it resolves and I get a response.

@CommanderRedYT
Copy link

I have the same problem. My DNS server (pihole, via dhcp) has IPv6 responses disabled and dig confirms that. Still, somehow this program tries to connect via IPv6

@louislam
Copy link
Owner

#2321 I guess it may be a similar issue.

@github-actions
Copy link

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 github-actions bot added the Stale label Feb 19, 2023
@github-actions
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants