-
Notifications
You must be signed in to change notification settings - Fork 836
Can not access the konga #57
Comments
Hi @koyuhau , Konga has no limit access to IP. When you say "cannot access" what do you mean? Can't access the server? Are there any Logs available? Have you setup Konga via docker or from source? On what port is it running? Can all the PCs ping the server where Konga is deployed on port 1337? |
"cannot access" means that there is no reaction using the browser to access port 1337. And all the PCs can ping the server. |
If you open the javascript console on the browsers that can't access,, are there any logs? |
It nothing and just say ERR_CONNECTION_REFUSED |
That means that the connection is rejected. Is there a chance that a firewall is blocking the connection to the specific port? Try # telnet {your-server-ip} 1337 |
I restart the konga,there is no problem. |
Thank you for your help, again appear this kind of circumstance, I telnet 1337 again. |
When start up the service, found that I and a few colleagues can access the service, but there are also some other colleagues can't access.This should have nothing to do with the browser.
Do konga have to limit access to IP or amount, or is this a bug?
The text was updated successfully, but these errors were encountered: