Help › When something does not work › H8
The device is rejected
The device says "Dieser Rechner ist nicht angemeldet" (this computer is not signed in), the console says "Rejected". What each reason means — places full, no access, certificate, block, licence — and who can fix it.
Preview this guide has not yet been clicked through on a real device. Button names and steps come from the program but may differ in details.
- For
- Private helper · Account administrator
- Applies to
- Free · Cloud · Own relay
- Controlled device
- Windows · macOS · Linux
- from version
- 20261010.3
What it is for
A device signs in at the relay, and the relay says no. Then nobody can reach the device. BrowserDesk states the reason in two places: on the device itself and in the console. Most reasons can only be fixed by the administrator of the access or of the relay — on the device neither a restart nor a reinstallation helps then.
What you need
- On the device: being able to open BrowserDesk.
- For most remedies: administrator rights in the console of your access (the console calls the access "tenant") or the operator of your relay.
How to do it
- Read the reason on the device. Open BrowserDesk → on the left Dashboard → card Ihr Desktop (Your desktop). There is the red box "Dieser Rechner ist nicht angemeldet" (this computer is not signed in) with the relay's sentence. Under Fernzugriff → Erreichbarkeit (Remote access → Reachability) it says "Nicht angemeldet" (not signed in).
- Or in the console. Overview → Needs attention → Devices rejected at registration (24 h). The list gives the reason for each device and the next step. In the device list the device is shown as Rejected; point at it with the mouse to see the reason.
- Look the reason up in this table and fix it:
| Sentence on the device (shortened) | Meaning | Remedy | |---|---|---| | "Die Anmeldung am Zugang wurde abgelehnt — der Beitritt ist abgelaufen oder wurde widerrufen. …" (sign-in to the access refused — the join has expired or was revoked) | The device's proof for the access is no longer valid — for example because the password of the account it joined through was changed (H23). | Join again on the device: EinstellungenFernzugriff (Settings > Remote access) → card Zugang (Access) → Beitreten (Join) — or with a one-time code from the console (C2). The sentence mentions "„Zugang beitreten“" (join access); this button is meant. | | "Diesen Zugang gibt es am Server nicht (mehr). …" (this access does not exist on the server (any more)) | The access the device wants to belong to does not exist at the relay. | Join an existing access (C2). | | "Der Server kennt für diesen Rechner ein Zertifikat, das hier nicht mehr vorliegt. …" or "Das Gerätezertifikat wurde vom Server abgelehnt …" (certificate missing here / rejected by the server) | The device certificate is missing on the device or no longer valid. | Administrator: open the device in the console → Reset certificate. The button is shown on the device while it is rejected, otherwise in the menu (⋮) under "Security". The device then fetches a new certificate. | | "Dieser Rechner wurde in der Verwaltung gesperrt. …" (this computer was blocked in the administration) | The device is blocked. | Administrator: menu (⋮) of the device → Unblock. | | "Der Server nimmt diesen Rechner nicht an: die Lizenz des Relays ist ausgeschöpft oder abgelaufen. …" (the relay's licence is exhausted or expired) | The licence of the own relay is not enough. | The relay operator extends or renews the licence (A7). | | "Für diesen Zugang auf browserdesk.de sind alle Plätze belegt …", "Für diesen Mandanten sind … Geräte gekauft. …" or "BrowserDesk Free umfasst bis zu … Geräte. …" (all places of the access are taken) | All places of the access are in use. | Administrator: release a device that is no longer needed with Free up place (C7) or buy more places (A7). | | "Dieses Gerät wurde aus seinem Zugang entfernt (Platz freigegeben). …" (removed from its access) | Someone took the device out of the access. | Add the device again (C2). | | "Diese Geräte-Kennung ist am Server gerade anderweitig angemeldet …" (this ID is signed in elsewhere) | The same ID is signed in twice, for example through a second installation. | Wait a moment. If it stays: click Neu registrieren (register again) in the box. |
- Wait. A rejected device tries again every two minutes. After the remedy it is back after about two minutes at the latest. If BrowserDesk on the device restarts once by itself shortly afterwards, that is intended: the device has then received its own proof for the access.
- Done? Then acknowledge. In the overview the entry disappears by itself as soon as the device signs in again. An entry for a device you have deleted is removed with Acknowledge.
How you know it worked
- On the device the red box is gone, and under Erreichbarkeit it says "Bereit" or "Bereit (Dienst)" (ready).
- In the console the device is no longer listed as Rejected.
What the other side sees
Whoever wants to connect to a rejected device gets "Gerät ist offline" (device is offline) or "unknown or offline host" (H7).
Good to know
- Restarting and reinstalling do not help with these reasons. Almost always something must be changed in the console or on the licence.
- Trusted networks do not affect the device's sign-in, only from where someone may control the device (D9, B7).
- More places in the middle of the term: there is no separate way for that on the website yet — write to info@browserdesk.de. For prices: Prices.
- Macs and computers without the service that were moved to another access dropped out again one day later before version 20261011.25. Update BrowserDesk on the device and join once more.
- The box always advises "Zertifikat zurücksetzen" (reset certificate). Below every red box it says "Das braucht Ihr Administrator: … Zertifikat zurücksetzen" (your administrator needs to … reset certificate). That only fits the certificate cases; otherwise the remedy from the table applies.
If it does not work
| You see | Meaning and remedy |
|---|---|
| Still rejected after Reset certificate | Wait two minutes until the device tries again. If it stays, report it (last row). |
| A sentence that is not listed here, or "Der Server hat die Anmeldung abgelehnt (Code: …)" (the server refused the sign-in) | Update BrowserDesk on the device; if it stays, report the code. |
| The device is not in the list, but the counter shows a rejection | The device names an access that does not exist — then it is in no device list. Join an existing access on the device. |
| None of this helps | Collect logs on the device (H19) and write to info@browserdesk.de with the ID, the time and the sentence from the box. |
Related
- H7 The device is offline or does not show up
- H23 "After the new password all computers of the access were gone"
- H24 "A device dropped out of the access"
- C2 Add a device to your own access
- C7 Remove or replace a device, or free up its place
- A6 Buy add-on modules and functions later — and understand seats per device
- A7 More devices or technicians, renewal, reminder before expiry
- G20 Understand why a device was rejected when signing in
- D9 Understand why the connection does not work
- H19 Collect logs and send them to support