Can't access update.lucee.org from server

dev support
1

Hello,

I encounter a problem with lucee on a dedicated OVH server : the server can’t access update.lucee.org. The resolver give the correct IP, but it is imposible to connect to update.lucee.org, neither via https or even a simple ping.

I set up a similar server (same hardware, same provider, same OS) few month ago, and it has no problems, but on the new server it don’t work.

Is the server IP blacklisted ?

OS: Ubuntu 18.04.5 LTS
Java Version: 11.0.7 (AdoptOpenJDK) 64bit
Tomcat Version: Apache Tomcat/9.0.35
Lucee Version: Lucee 5.3.6.61

Regards,

2

I’d say: If you are connected to the internet then nothing should block that IP, unless there is some sort of firewall in your OS or your ISP is blocking the connection. Did you try a traceroute already? Where does the hop get the last ping back?

3

Thank you for your reply Andreas,

The server is connected to the internet, there is a firewall but it don’t filter this connexion - and is configured as the working server . I don’t think my ISP is blocking the connection, this isn’t their policy, and the other server at the same ISP is working.

My traceroute is :


traceroute to 205.210.189.210 (205.210.189.210), 30 hops max, 60 byte packets
 1  135.125.2.252 (135.125.2.252)  0.509 ms  0.489 ms  0.582 ms
 2  10.162.147.52 (10.162.147.52)  0.601 ms  0.687 ms 10.162.147.50 (10.162.147.50)  0.538 ms
 3  10.72.50.80 (10.72.50.80)  0.675 ms 10.72.50.84 (10.72.50.84)  0.776 ms 10.72.50.92 (10.72.50.92)  0.907 ms
 4  10.73.16.246 (10.73.16.246)  0.157 ms 10.73.16.240 (10.73.16.240)  0.139 ms  0.162 ms
 5  10.95.64.2 (10.95.64.2)  1.148 ms 10.95.64.138 (10.95.64.138)  0.551 ms 10.95.64.134 (10.95.64.134)  0.790 ms
 6  lon-drch-sbb1-nc5.uk.eu (54.36.50.230)  4.453 ms  4.475 ms lon-thw-sbb1-nc5.uk.eu (54.36.50.240)  4.201 ms
 7  be100-1295.nwk-1-a9.nj.us (192.99.146.127)  70.343 ms be100-1298.nwk-5-a9.nj.us (192.99.146.133)  73.042 ms be100-1295.nwk-1-a9.nj.us (192.99.146.127)  73.836 ms
 8  be102.bhs-g2-nc5.qc.ca (192.99.146.138)  81.562 ms be102.bhs-g1-nc5.qc.ca (198.27.73.204)  93.211 ms *
 9  be100-1324.chi-5-a9.il.us (192.99.146.141)  98.184 ms  99.874 ms be100-1320.chi-1-a9.il.us (198.27.73.207)  96.913 ms
10  be103.pdx-prt1-sbb1-nc5.oregon.us (142.44.208.161)  143.659 ms be103.pdx-pdx02-sbb1-nc5.oregon.us (142.44.208.159)  143.103 ms  141.867 ms
11  10.200.1.1 (10.200.1.1)  144.659 ms 10.200.1.3 (10.200.1.3)  146.519 ms 10.200.1.1 (10.200.1.1)  147.865 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

As you indicate that there is no reason of being blacklisted at lucee server, I’m opening a support request at my ISP at the same time.

Regards,

4

What do you get in your browser when you hit a URL like http://update.lucee.org/rest/update/provider/list

5

Thank you for your reply bdw429s,

As It’s a linux server, I use lynx browser via command line (and I’m French so messages are in french) :

$ lynx http://update.lucee.org/rest/update/provider/list

Recherche update.lucee.org
Connexion HTTP à update.lucee.org
Alerte ! : Impossible d’établir une connexion à l’hôte distant.

lynx : accès impossible au fichier de départ http://update.lucee.org/rest/update/provider/list

I tried with telnet to port 80, it’s the same, timeout.

I opened a ticket at my ISP support desk asking if there is a blacklist or route problem at their side, I’m waiting for their answer.

Regards

1 Like
6

try with https?

7

This hop is a private non-routable address as of RFC1918. I’d definitively ask the ISP to take a look at that trace.

8

@Zackster

With https, it’s the same :

$ lynx https://update.lucee.org/rest/update/provider/list

Recherche update.lucee.org
Connexion HTTPS à update.lucee.org
Alerte ! : Impossible d’établir une connexion à l’hôte distant.

lynx : accès impossible au fichier de départ https://update.lucee.org/rest/update/provider/list

@andreas

This hop is also present when it works - form the other server :

traceroute to 205.210.189.210 (205.210.189.210), 30 hops max, 60 byte packets
 1  51.77.246.252 (51.77.246.252)  0.490 ms  0.584 ms  0.718 ms
 2  10.161.154.14 (10.161.154.14)  0.611 ms  0.700 ms  0.826 ms
 3  10.17.115.14 (10.17.115.14)  0.537 ms 10.17.115.12 (10.17.115.12)  0.477 ms 10.17.115.4 (10.17.115.4)  0.613 ms
 4  10.73.16.154 (10.73.16.154)  0.145 ms 10.73.16.152 (10.73.16.152)  0.101 ms  0.107 ms
 5  10.95.64.0 (10.95.64.0)  1.001 ms 10.95.64.132 (10.95.64.132)  0.473 ms  0.484 ms
 6  lon-thw-sbb1-nc5.uk.eu (54.36.50.240)  4.138 ms  4.261 ms  4.246 ms
 7  be100-1295.nwk-1-a9.nj.us (192.99.146.127)  75.081 ms  73.546 ms  75.543 ms
 8  be102.bhs-g2-nc5.qc.ca (192.99.146.138)  84.285 ms be102.bhs-g1-nc5.qc.ca (198.27.73.204)  81.536 ms  84.949 ms
 9  be100-1320.chi-1-a9.il.us (198.27.73.207)  96.191 ms be100-1324.chi-5-a9.il.us (192.99.146.141)  101.383 ms be100-1320.chi-1-a9.il.us (198.27.73.207)  99.447 ms
10  be103.pdx-prt1-sbb1-nc5.oregon.us (142.44.208.161)  139.257 ms be103.pdx-pdx02-sbb1-nc5.oregon.us (142.44.208.159)  140.220 ms  138.651 ms
11  10.200.1.1 (10.200.1.1)  153.744 ms  149.375 ms  147.321 ms
12  * * *
13  be1.cr2-sea-a.bb.as11404.net (174.127.149.136)  143.294 ms  145.480 ms  145.323 ms
14  gateway.viviotech.net (216.243.28.218)  157.150 ms  155.235 ms  158.843 ms
15  * * *

But I read the hop 13 as the first hop outside my ISP provider, so I think the problem is there. I’m waiting for their reply, I will tell you if they resolve the problem.

9

Hello,

My ISP have found a problem with the routing of the server on their network, and solved it, so now it works !

Thanks to all for your help

Wishing you a good day

1 Like
10

You’re always welcome! If you have any future questions, please feel always free to post.