There are several possible reasons for a 403. Some you might be able to remedy yourself.
Browser Cache - Clear cache, at least for the domain (my.n8n.host) your browser is using to reach the n8n UI. Or, if using Chrome or similar browser, try the request in an incognito window.
Proxy/VPN interference - If you are running n8n in an environment where outbound calls to certain domains might be blocked on your own network, either remove the rule that is blocking access or configure the machine running n8n to use a client-side VPN (so the request to n8n’s system (enterprise.n8n.io) goes around the outbound proxy/vpn… provided you are even allowed to do this).
Server-Side Block - It’s possible, but unlikely, that enterprise.n8n.io (the license server) has rules preventing access from some networks/ip-blocks. A client-side VPN connection to originate the traffic from another place/source-ip might help here too (or at least confirm whether that’s the issue).
If none of this helps, add some more context information here, which might help someone identify where things could be going wrong.
I switched back to Digital Ocean. And the issue don’t happen there. Everything is smooth.
Don’t get this error, or the problems with credentials for GHL. for firewall I didn’t modify any on Hetzner but did directly in the server with ufw. Not sure if that had anything to do with it