You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever running ntfy sub https://my-own-ntfy-server.com/TOPIC the command stays idle and doesn't listen to any messages coming to this topic when the servers are routed through cloudflare tunnels. It gives a 524 after a while.
The server that is hosting ntfy is behind cloudflare tunnels because of my limited network. Cloudflare tunnels enforce using https therefore using http is not an option. Cloudflare supports wss as shown
Also the server and command is completely fine when connecting through my local network:
ntfy sub http://192.168.100.128/JIDLO
{"id":"IxsiF9K1CguP","time":1736120908,"expires":1736164108,"event":"message","topic":"JIDLO","message":"JIDLO","priority":3}
Curl looks the same on both
curl to the local server
curl http://192.168.100.128/JIDLO
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<title>ntfy web</title>
<!-- Mobile view -->
<meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1,user-scalable=no" />
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
<meta name="HandheldFriendly" content="true" />
<!-- Mobile browsers, background color -->
<meta name="theme-color" content="#317f6f" />
<meta name="msapplication-navbutton-color" content="#317f6f" />
<meta name="apple-mobile-web-app-status-bar-style" content="#317f6f" />
<link rel="apple-touch-icon" href="/static/images/apple-touch-icon.png" sizes="180x180" />
<link rel="mask-icon" href="/static/images/mask-icon.svg" color="#317f6f" />
<!-- Favicon, see favicon.io -->
<link rel="icon" type="image/png" href="/static/images/favicon.ico" />
<!-- Previews in Google, Slack, WhatsApp, etc. -->
<meta
name="description"
content="ntfy lets you send push notifications via scripts from any computer or phone. Made with ❤ by Philipp C. Heckel, Apache License 2.0, source at https://heckel.io/ntfy."
/>
<meta property="og:type" content="website" />
<meta property="og:locale" content="en_US" />
<meta property="og:site_name" content="ntfy web" />
<meta property="og:title" content="ntfy web" />
<meta
property="og:description"
content="ntfy lets you send push notifications via scripts from any computer or phone. Made with ❤ by Philipp C. Heckel, Apache License 2.0, source at https://heckel.io/ntfy."
/>
<meta property="og:image" content="/static/images/ntfy.png" />
<meta property="og:url" content="https://ntfy.sh" />
<!-- Never index -->
<meta name="robots" content="noindex, nofollow" />
<!-- Style overrides & fonts -->
<link rel="stylesheet" href="/static/css/app.css" type="text/css" />
<link rel="stylesheet" href="/static/css/fonts.css" type="text/css" />
<!-- PWA -->
<link rel="manifest" href="/manifest.webmanifest" />
<script type="module" crossorigin src="/static/media/index-9e24212a.js"></script>
</head>
<body>
<noscript>
ntfy web requires JavaScript, but you can also use the
<a href="https://ntfy.sh/docs/subscribe/cli/">CLI</a> or <a href="https://ntfy.sh/docs/subscribe/phone/">Android/iOS app</a> to
subscribe.
</noscript>
<div id="root"></div>
<script src="/config.js"></script>
</body>
</html>
The text was updated successfully, but these errors were encountered:
🐞 Describe the bug
Whenever running
ntfy sub https://my-own-ntfy-server.com/TOPIC
the command stays idle and doesn't listen to any messages coming to this topic when the servers are routed through cloudflare tunnels. It gives a 524 after a while.💻 Components impacted
💡 Screenshots and/or logs
curl to the server
listening to websockets using wscat
🔮 Additional context
The server that is hosting ntfy is behind cloudflare tunnels because of my limited network. Cloudflare tunnels enforce using https therefore using http is not an option. Cloudflare supports wss as shown
Also the server and command is completely fine when connecting through my local network:
Curl looks the same on both
curl to the local server
The text was updated successfully, but these errors were encountered: