Notification error codes
When notification setup stops, bighelp shows a short message and a code, like Code NS-102. The message says what to do. The code says which step stopped.
Ask a questionWhere do I see the code?
- In Settings › Notifications, under the message.
- In the Notifications step of first setup.
- In Settings › Notifications › Advanced › Provider details, next to Last setup problem.
When trying again can help, bighelp shows Check Again. When it can't, the message tells you what to do instead.
How do I send a code to us?
- Tap Copy Details next to the code.
- Paste it in a GitHub issue.
The details hold the code, the step that stopped, the kind of error, your bighelp version and your device's system version. They never hold your computer's address, your name, a token or an ID.
Two fixes many codes use
- Set Up Again: in Settings › Notifications, tap Set Up Again. It clears this computer's notification setup, on the computer and on this device, and sets it up fresh.
- Turn off, then on: at the bottom of Settings › Notifications, tap Turn Off Notifications. Then turn notifications on again with Enable Notifications.
On a Mac, "iOS Settings" below means System Settings. On Vision Pro, it means Settings.
NS-1xx: the notification service
bighelp's notification service, and this device's sign-up with it.
| Code | What it means | What to do |
|---|---|---|
| NS-101 | This device is offline. | Connect to Wi-Fi or mobile data, then try again. |
| NS-102 | bighelp can't reach its notification service from this device. | Check that this device is online and that no VPN or DNS filter blocks it, then try again. If you use a VPN, DNS filter or firewall, let it allow link.loopdy.app. |
| NS-103 | bighelp's notification service took too long to answer. | Wait a minute, then try again. |
| NS-104 | This device couldn't make a secure connection to bighelp's notification service. | Check the device's date and time, and turn off any VPN or filter that inspects web traffic. Then try again. |
| NS-105 | bighelp's notification service sent an answer bighelp can't read. | If this Wi-Fi has a sign-in page, sign in with Safari first, or use another network. Then try again. |
| NS-106 | bighelp's notification service has a problem right now. | Try again later. |
| NS-107 | bighelp's notification service is busy. | Wait a few minutes, then try again. |
| NS-108 | A network problem stopped setup. | Check this device's connection, then try again. |
| NS-109 | bighelp's notification service doesn't accept a request from this version of bighelp. | Update bighelp. If it still happens, send us this code and its details. |
| NS-110 | bighelp's notification service turned down a step for a reason this version of bighelp doesn't know. | Update bighelp. If it still happens, send us this code and its details. |
| NS-111 | bighelp's notification service already has a different key for this device. | Turn off notifications at the bottom of Settings › Notifications, then turn them on again. |
| NS-112 | bighelp's notification service got the same sign-up twice. | Try again. |
| NS-113 | This device's clock is wrong. | In iOS Settings, go to General › Date & Time and turn on Set Automatically. Then try again. |
| NS-114 | This network made too many notification sign-ups in the last hour. | Wait one hour, then try again. |
| NS-115 | bighelp's notification service can't take new sign-ups right now. | Try again later. |
| NS-116 | bighelp's notification service didn't accept this device's new key. | Update bighelp. If it still happens, send us this code and its details. |
| NS-117 | bighelp's notification service didn't accept this device's sign-in. | Usually this device's clock is wrong: in iOS Settings, go to General › Date & Time and turn on Set Automatically. Then try again. |
| NS-118 | bighelp's notification service ended this device's notification sign-up. | Turn off notifications at the bottom of Settings › Notifications, then turn them on again. |
| NS-119 | bighelp's notification service didn't accept this device's notification key. | Turn off notifications at the bottom of Settings › Notifications, then turn them on again. |
| NS-120 | bighelp's notification service got the same request twice. | Try again. |
| NS-121 | bighelp's notification service didn't confirm that it removed this device's old sign-up. | Try again later. |
| NS-122 | bighelp's notification service couldn't finish removing this device from the push service. | Try again later. |
NS-2xx: this device
Notification permission on this device, its push registration and the setup bighelp saves here.
| Code | What it means | What to do |
|---|---|---|
| NS-201 | Notifications for bighelp are off. | In iOS Settings, go to Notifications › bighelp and turn on Allow Notifications. Then try again. |
| NS-202 | iOS didn't answer when bighelp asked to send notifications. | Try again. |
| NS-203 | iOS couldn't register this device for notifications. | Check that the device is online and signed in to your Apple Account, then try again. Restarting the device can help. |
| NS-204 | iOS took too long to register this device for notifications. | Check the device's connection, then try again. |
| NS-205 | iOS didn't give bighelp this device's notification address. | Try again. |
| NS-206 | The push service couldn't register this device. | Wait a minute, then try again. |
| NS-207 | The push service didn't confirm this device's registration. | Try again. |
| NS-208 | bighelp couldn't move your saved alert choices to the push service. | Try again. |
| NS-209 | This device's registration didn't finish before bighelp checked it. | Try again. |
| NS-210 | This device's sign-in with the push service stopped during setup. | Try again. |
| NS-211 | bighelp can't reach the push service from this device. | Check that this device is online and that no VPN or DNS filter blocks it, then try again. If you use a VPN or DNS filter, let it allow Apple push notifications. |
| NS-212 | The push service didn't accept this device's sign-in. | Wait a minute, then try again. |
| NS-213 | The push service sent an answer bighelp can't read. | Try again later. |
| NS-214 | The push service didn't start in bighelp. | Quit bighelp and open it again. |
| NS-215 | This copy of bighelp can't use notifications. | Install bighelp from the App Store or TestFlight. |
| NS-216 | This copy of bighelp can't use notifications. | Install bighelp from the App Store or TestFlight. |
| NS-217 | bighelp changed how it gets notifications. | Quit bighelp and open it again. |
| NS-218 | bighelp doesn't know which push service to use. | Quit bighelp and open it again. If it still happens, send us this code and its details. |
| NS-219 | Notifications don't work in demo mode. | Connect your own computer. |
| NS-220 | bighelp's notification service isn't ready to send notifications right now. | Try again later. |
| NS-221 | The push service doesn't know this device yet. | Wait a minute, then try again. |
| NS-222 | The push service hasn't confirmed this device's sign-in yet. | Wait a minute, then try again. |
| NS-223 | bighelp's notification service can't send to this kind of bighelp build right now. | Try again later. If it still happens, send us this code and its details. |
| NS-224 | The push service has a different notification address for this device. | Try again. |
| NS-225 | The push service has notifications turned off for this device. | Check that notifications for bighelp are on in iOS Settings, then try again. |
| NS-226 | The push service marked this device as inactive. | Try again. |
| NS-227 | The push service has this device registered for another kind of bighelp build (TestFlight or App Store). | Try again. |
| NS-228 | The push service doesn't have every alert type for this device yet. | Wait a minute, then try again. |
| NS-229 | The push service confirmed a different registration for this device. | Try again. |
| NS-230 | The push service's check of this device didn't pass. | Wait a minute, then try again. |
| NS-231 | bighelp's notification service can't reach the push service right now. | Try again later. |
| NS-232 | bighelp's notification service got an answer from the push service that it can't use. | Try again later. |
| NS-233 | The push service's records for this device don't match. | Try again. |
| NS-234 | The push service has more than one registration for this device. | Turn off notifications at the bottom of Settings › Notifications, then turn them on again. |
| NS-235 | bighelp's notification service isn't set up to use the push service right now. | Try again later. If it still happens, send us this code and its details. |
| NS-240 | bighelp couldn't open this device's keychain. | Unlock the device, then try again. |
| NS-241 | bighelp's saved notification setup on this device is damaged. | Turn off notifications at the bottom of Settings › Notifications, then turn them on again. |
| NS-242 | bighelp couldn't save notification setup on this device. | Check that the device has free space, then try again. |
| NS-243 | bighelp couldn't load notification setup on this device. | Quit bighelp and open it again. |
NS-3xx: your computer
The connection to your computer, the bighelp plugin and Hermes.
| Code | What it means | What to do |
|---|---|---|
| NS-301 | bighelp can't reach this computer. | Check that the computer is on and Hermes is running, then try again. |
| NS-302 | bighelp lost the connection to this computer. | Check the computer's address, your VPN or Tailscale, and that Hermes is running. Then try again. |
| NS-303 | This computer took too long to answer. | Try again. |
| NS-304 | bighelp couldn't check this computer's secure connection. | Check the computer's HTTPS certificate, then try again. |
| NS-305 | This computer sent an answer bighelp can't read. | Update the bighelp plugin on the computer, then try again. |
| NS-306 | Hermes on this computer had a problem. | Look in Hermes' logs, then try again. |
| NS-307 | This computer is getting too many requests. | Wait a minute, then try again. |
| NS-308 | This computer didn't accept bighelp's sign-in. | Sign in to this computer again, then try again. |
| NS-309 | This computer doesn't have the notification part of the bighelp plugin. | Update the plugin and restart Hermes, then try again. See update the plugin. |
| NS-310 | This computer's sign-in changed. | Sign in to this computer again, then try again. |
| NS-311 | The bighelp plugin on this computer turned down a step. | Update the plugin, then try again. If it still happens, send us this code and its details. |
| NS-312 | The bighelp plugin on this computer doesn't accept a request from this version of bighelp. | Update bighelp and the plugin. If it still happens, send us this code and its details. |
| NS-320 | bighelp couldn't reach GitHub to get the newest bighelp plugin. | Check this device's internet connection, then try again. |
| NS-321 | This computer has more than one bighelp plugin. | Remove the extra one in Hermes, then try again. |
| NS-322 | An earlier plugin install on this computer didn't finish. | Use Set Up Again in Settings › Notifications. |
| NS-323 | This version of Hermes can't install plugins for bighelp. | Update Hermes, or install the bighelp plugin on the computer. Then try again. |
| NS-324 | This computer doesn't let bighelp install plugins. | Allow it in Hermes, or install the bighelp plugin on the computer. Then try again. |
| NS-325 | Hermes on this computer refused the bighelp plugin. | Look in Hermes for the reason, then try again. |
| NS-326 | Hermes on this computer refused to change its plugins. | Look in Hermes for the reason, then try again. |
| NS-327 | The plugin install may still be running on this computer. | Wait a minute, then try again. |
| NS-328 | This computer didn't confirm the plugin install. | Try again. If it still happens, use Set Up Again. |
| NS-329 | The bighelp plugin didn't turn on. | Turn it on in Hermes, then try again. |
| NS-330 | Hermes hasn't loaded the notification part of the plugin yet. | Restart Hermes on this computer (the hermes serve process, not only the messaging gateway), then try again. See how to restart Hermes. |
| NS-331 | The bighelp plugin on this computer is too old for notifications. | Update the plugin, then try again. See update the plugin. |
| NS-340 | This computer can't reach bighelp's notification service. | Check the computer's internet connection and that no firewall blocks it, then try again. If the computer has a firewall, let it allow link.loopdy.app. |
| NS-341 | This computer's network sent its connection to bighelp's notification service somewhere else. | Check the computer's proxy settings, then try again. |
| NS-342 | This computer got an answer from bighelp's notification service that it can't read. | Check the computer's network and proxy, then try again. |
| NS-343 | bighelp's notification service turned down this computer's request. | Use Set Up Again. |
| NS-344 | This device's notification permission doesn't match this computer's key. | Use Set Up Again. |
| NS-345 | This computer got a notification permission it can't read. | Try again later. |
| NS-346 | This computer says the notification permission ran out. | Check that the computer's clock is right, then use Set Up Again. |
| NS-347 | This computer already sends notifications to the most devices it can. | Send us this code and its details. |
| NS-348 | This computer has a different copy of this device's notification permission. | Use Set Up Again. |
| NS-349 | The bighelp plugin can't keep its notification files private on this computer. | Check the permissions of Hermes' home folder, then try again. |
| NS-350 | Hermes on this computer runs on a system that bighelp notifications don't support yet. | Send us this code and its details. |
| NS-351 | The bighelp plugin's notification key on this computer is damaged. | Send us this code and its details. |
| NS-352 | This computer doesn't have this device's notification permission anymore. | Use Set Up Again. |
| NS-353 | This computer's copy of this device's notification permission changed. | Use Set Up Again. |
| NS-354 | This computer didn't accept this device's alert key. | Update bighelp. If it still happens, send us this code and its details. |
| NS-355 | This computer refused alerts for the open chat's agent. | Use Set Up Again. |
| NS-356 | This computer couldn't turn on alerts for the open chat. | Try again. |
| NS-360 | This computer confirmed a different notification permission. | Use Set Up Again. |
| NS-361 | This computer's notification setup changed while bighelp checked it. | Try again. |
| NS-362 | This computer didn't confirm this device's alert key. | Try again. |
| NS-363 | This computer didn't confirm alerts for the open chat. | Try again. |
NS-4xx: notification permissions
A notification permission is the record that lets one computer notify this device.
| Code | What it means | What to do |
|---|---|---|
| NS-401 | bighelp's notification service has an earlier try with different details for this computer. | Use Set Up Again. |
| NS-402 | This device has too many notification permissions, or two of them conflict. | Use Set Up Again. If it still happens, send us this code and its details. |
| NS-403 | bighelp's notification service doesn't know this computer's notification permission. | Use Set Up Again. |
| NS-404 | The notification permission changed while bighelp updated it. | Try again. |
| NS-405 | Another notification permission already uses this computer's key with bighelp's notification service. | Use Set Up Again. |
| NS-406 | This device's clock is wrong. | In iOS Settings, go to General › Date & Time and turn on Set Automatically. Then try again. |
| NS-407 | This computer's notification permission isn't active anymore. | Use Set Up Again. |
| NS-408 | This device's notification sign-up is from an older version of bighelp. | Turn off notifications at the bottom of Settings › Notifications, then turn them on again. |
| NS-409 | This device's notification sign-up uses a kind of sign-in that bighelp retired. | Turn off notifications at the bottom of Settings › Notifications, then turn them on again. |
| NS-420 | This computer's notification key changed since this device was set up. | Use Set Up Again. |
| NS-421 | bighelp's notification service didn't confirm that it removed an old notification permission. | Try again. |
| NS-422 | This computer has more than one old notification permission. | Use Set Up Again. |
| NS-423 | This computer has more than one notification permission for this device. | Use Set Up Again. |
| NS-424 | The notification permission doesn't match the one saved on this device. | Use Set Up Again. |
| NS-425 | The notification permission request saved on this device is damaged or out of date. | Use Set Up Again. |
| NS-426 | The new notification permission doesn't match what bighelp asked for. | Use Set Up Again. |
| NS-427 | The notification permission didn't pass bighelp's checks. | Use Set Up Again. |
| NS-428 | This notification permission belongs to another computer on this device. | Use Set Up Again. |
| NS-429 | An earlier change to notifications isn't finished. | Wait a minute, then try again. |
NS-5xx: turning notifications off
Turn Off Notifications shows these when it can't finish.
| Code | What it means | What to do |
|---|---|---|
| NS-501 | Notifications aren't fully off yet, because bighelp can't reach its notification service. | Check this device's connection, then try again. |
| NS-502 | Notifications aren't fully off yet, because bighelp's notification service didn't confirm. | Try again later. |
| NS-503 | Notifications aren't fully off yet, because bighelp's notification service turned down the request. | Try again. If it still happens, send us this code and its details. |
| NS-504 | Notifications aren't fully off yet, because bighelp couldn't delete their data on this device. | Unlock the device, then try again. |
| NS-505 | Turning off notifications stopped before it finished. | Try again. |
NS-9xx: other problems
| Code | What it means | What to do |
|---|---|---|
| NS-901 | Setup stopped because something changed while it ran. | Try again. |
| NS-902 | Setup is already running for this computer. | Wait for it to finish. |
| NS-903 | bighelp hit a problem of its own. | Update bighelp. If it still happens, send us this code and its details. |
| NS-999 | Something unexpected stopped setup. | Try again. If it still happens, send us this code and its details. |
NS-123 to NS-126 and NS-510 to NS-513 only go to the device's log. bighelp tries again later by itself, and alerts keep arriving. You never need to act on them.