-
Notifications
You must be signed in to change notification settings - Fork 138
Troubleshooting
Access Denied.
is a cryptic message that Gateway sends when it receives a request from an IP address it doesn't allow requests from. To fix it specify your client's IP address in the conf.yaml
under ips/allow
and ensure your IP is not listed in ips/deny
.
Eg.:
ips:
allow:
10.148.0.0
10.149.*
Learn how to provide IBeam with a custom conf.yaml
in Gateway Configuration section.
This error can also appear when communicating with a locally running IBeam image using 'localhost' as the hostname of your request. To fix this, ensure 172.17.0.*
is listed in the ips/allow
. See #15 for more.
This should only appear if you use your own TLS certificates. It means your certificate was created without specifying the client host IP or DNS you're trying to communicate from. You will need to recreate your certificates including the IP or DNS of the machine you're communicating from.
See the optional SAN specification in Step 1 of either Keytool or OpenSSL certificate generation.
There are some indications that the IP location from which you are attempting to log in may define whether this error could appear. Some users have observed that using a VPN can help with this issue.
See https://github.com/Voyz/ibeam/issues/100 for more.
See any error on this page? Create an Issue and let us know.