## The problem

Shipping logs to the service URL for that host and port returns `401: Logging token is not valid`, even with a freshly created token. The token is valid, and the same token works against `listener.logz.io:8071`.

## The fix

The listener URL depends on where your account lives, not where you are. Accounts default to the US region; if your app URL contains `app.logz.io` your account is US and you must ship to `listener.logz.io:8071`, not `listener-eu.logz.io:8071`. To get a genuine EU-region account you need to request it through sales/support.