Hello, I have an external kong that act has a gateway "http://api.company.fr" to multiples api that are on azure virtual machines, OS is debian everywhere. I have also an internal kong to make the links between the external kong and the azure virtual machines Yetserday for some reason, the internal kong rebooted. the error wasn't explained in azure and it lasted only 45seconds. Anyway it was successfuly rebooted but since that i can't call API on the port 8000, I get "connection refused". I guess the port has been closed but even tough i re opened them with "sudo ufw allow 8000" and "sudo iptables -I INPUT -p tcp -m tcp --dport 8000 -j ACCEPT" it still doesn't work "connection refused) I also check and even re created the incoming traffic rules to allow port 8000 depending of my house IP or IP of the virtual machine of the API. nothing has changed.. I also rebooted the external kong and since that i can't even access to it with SSH, i allowed the incoming traffic rules from my IP to port 22 with azure portal , recreated the ssh key and tried to connected. I get error timeout

Hi @MYRE, Axel You can connect via serial console too, and access your Linux and check if there are any restrictions, Reference: https://video2.skills-academy.com/en-us/troubleshoot/azure/virtual-machines/serial-console-linux You can disable the firewall for test (systemctl stop ufw) systemctl stop firewalld and Iptables -F Remembering that usually ssh root login is blocked Get in touch if you need more help with this issue. --please don't forget to "[Accept the answer]" if the reply is helpful--

Can't access to an azure virtual machine with SSH

Accepted answer

Jackson Martins 10,151 Reputation points MVP

2022-08-29T18:47:02.01+00:00

Hi @MYRE, Axel

You can connect via serial console too, and access your Linux and check if there are any restrictions,

Reference: https://video2.skills-academy.com/en-us/troubleshoot/azure/virtual-machines/serial-console-linux

You can disable the firewall for test (systemctl stop ufw) systemctl stop firewalld and Iptables -F

Remembering that usually ssh root login is blocked

Get in touch if you need more help with this issue.

--please don't forget to "[Accept the answer]" if the reply is helpful--
Please sign in to rate this answer.

1 person found this answer helpful.
Jackson Martins 10,151 Reputation points MVP

2022-08-29T18:54:14.25+00:00

@MYRE, Axel

Check that the sshd service is running, also check that there is no firewall restriction (iptables or other)

You can use "ip flow verify" in Network watcher and check that there is no overlap of permissions in NSG (there are cases where a rule applies at Vnet level and via NIC):

If denied, you can go to this nsg and allow the rule

MYRE, Axel 31 Reputation points

2022-08-29T19:15:43.99+00:00

Thanks for your answers,

I stopped iptables, ufw and firewalld with their commands and when i run "curl http://IP_KONG_INTERNAL:8000" from another virtual machine (in the same network) i still get "Failed to Connect http://IP_KONG_INTERNAL port 8000: Connection Refused"..

Jackson Martins 10,151 Reputation points MVP

2022-08-29T19:18:57.317+00:00

And localhost internal Telnet?

Telnet localhost 8080

Verify if service is listen on port by:

Netstat -tulpn

MYRE, Axel 31 Reputation points

2022-08-29T19:23:32.23+00:00

When i run "telnet localhost 8080" i get Unable to connect to remote host: Connection refused.

and when i run "netstat -tulpn"

Jackson Martins 10,151 Reputation points MVP

2022-08-29T19:27:50.743+00:00

On this screenshot has no service listen on port 8080

In this case, make sure the service is running and configuration is on port 8080

In ps aux | grep nameofservice

Can you see the service running?

Jackson Martins 10,151 Reputation points MVP

2022-08-29T19:34:49.143+00:00

The port ready for connection is:

22
7000
7199
68
123

MYRE, Axel 31 Reputation points

2022-08-29T23:17:02.897+00:00

Thanks a lot for your help

So i successfully allowed the ports 8000 in the internal kong.
I also noticed that i should had ran the Kong executable in the external kong which made some ports like (8001) opened and listening.

The external kong is made to being accessed as a base url from an url (api.company.com) but when i put this url in browser or even postman, it keeps loading for like 60seconds and it shows error timeout..

i created many rules on Azure to allow my IP, or even any IP to access this url at many ports but mostly 8000 for http and 8443 for https and it still load for 60 seconds and gives no answers..

Jackson Martins 10,151 Reputation points MVP

2022-08-30T10:05:34.81+00:00

Hi @MYRE, Axel

Were you able to connect via telnet? does the timeout only happen in the browser?

In this case, you can follow Kong's recommendations (increase timeout). There’s a discussion on the kongs Forum:

Reference: https://discuss.konghq.com/t/how-does-kong-handle-long-duration-requests/5645/5

Reference:https://support.konghq.com/support/s/article/How-to-configure-the-upstream-timeout-plugin?

Reference: https://www.gosysops.com/2021/how-to-set-kong-timeout-in-5-mins.html

Please "[Accept the answer]" if the information helped you. This will help us and others in the community as well.

MYRE, Axel 31 Reputation points

2022-08-30T13:47:26.23+00:00

Hello Martins,

Yes the serial console in azure and the 3 commands to disable the firewall helped to make the service back. I will find a way to just allow the right ports later.
Thanks a lot.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Can't access to an azure virtual machine with SSH

0 additional answers

Your answer