Sadly as mentioned, we do not block ports on our end, only ports we block is port 25 if our clients cause spam, we would suggest verifying the configurations of the services which are using port 3306 and to verify if the service is listening on that port which can be done using the command below in command-prompt with administrator permission:
C:\Users\username> netstat -anb -p TCP
On our end we can see that the port is closed when performing a port scan:
--------------------------------------------------------------------------------------
nmap -PN 0 -p 3306
Starting Nmap 7.80 (
Nmap: the Network Mapper - Free Security Scanner (https://nmap.org) ) at 2023-12-25 07:57 EST
Nmap scan report for vps-0feea792.vps.ovh.ca (0)
Host is up (0.011s latency).
PORT STATE SERVICE
3306/tcp closed mysql
Nmap done: 1 IP address (1 host up) scanned in 0.03 seconds
--------------------------------------------------------------------------------------
When looking into your Network Firewall configurations, you have no Refuse All IPv4 for rule 19 and the source and destination ports configured are not correctly done, the ports should be under destination if those ports have to be exposed to the internet of your server. Having destination and source port on 1 line will not work. You can also disable the Network Firewall to if you believe this is what is blocking the port, however before the Network Firewall was disabled and the port was still showing as closed on your servers end.
This would be technically out of our scope of support, since it is relating to software and configurations. You may have to do research online of the service you are configuring for more insight or perhaps reach out to a professional server administrator for further assistance or our partners.
