If the connection to PlentyOneBase fails with error messages such as "No connection to PlentyONE Base established" or "Not connected (No secure connection)", this may be due to a blocked permission in the Google Chrome browser.

This often occurs even though the standard error sources have already been checked.

Check known standard error sources

Before checking the browser settings, make sure the following common causes are excluded:

• Port check: The port (default 7331) is correctly occupied by PlentyOneBase and is not blocked.
• Access Token: The Access Token in the PlentyONE backend and in the local PlentyOneBase configuration are identical.
• Local firewall: The Windows Defender Firewall or third-party antivirus software does not block the connection (if necessary, disable temporarily for testing).
• DNS rebind protection: If you use a router such as the Fritz!Box, make sure that the domain local.plentybase.de has been added as an exception.

Solution: Check Chrome permission for local network

If the above points do not solve the problem, the cause is very likely a recent change in the Google Chrome browser.

After an update, Chrome explicitly asks whether a connection to devices in your local network is allowed.

• New prompt: If Chrome asks you when testing the connection whether the connection to devices in the local network should be allowed, select Allow.
• Already blocked: If you previously accidentally clicked Block, you must correct this setting in your Chrome settings. There, search for the permissions for local network devices and set the setting for PlentyONE back to "Allow".