Update sites can not be reached

Hello Jeroen,

I have just performed an extension update on the productive side twice.

Attempt 1:

The problem still existed, but only for the URL:
vi-solutions.de/updates/vfsubscription/j3/extension.xml

The problem no longer existed for the URL:
vi-solutions.de/updates/visforms/extension_vfbase.xml

Attempt 2:

The problem still existed, now for both URLs.

Logs on our update server:

The access log of our update server shows no request from the productive side.

Option:

Could you set up an FTP access with write permissions for the productive side for me (URL and login information via e-mail)?

I would like to use a small PHP script
- to check from your server in your web space
- outside of Joomla and without Joomla
- whether our update server can be reached from there.

The small PHP script runs a PHP variant of the popular command line tool 'ping'.
The command line tool 'ping' measures the response time of the addressed server.

Best regards, Ingmar

Hello Jeroen,

thanks for the FTP access data.
I tested access to our update server independently of Joomla with 2 small PHP scripts.

A domain resolution from 'vi-solutions.de' to our IP '178.254.7.138' is possible.
A connection is not possible.
It is not possible to establish a TCP connection on port 80 with our domain (vi-solutions.de) from your server.

The system on which the web server runs is a Windows Server.
You must contact your provider directly to find out the cause.

Your provider must trace the connection to our server.
This will enable them to determine where the route goes and where exactly it ends.

Here is a short trace result to domain 'vi-solutions.de' on the physical server 'xxx.1blu.de [178.254.7.138]' executed from a local Windows system.

windows-command-line> tracert vi-solutions.de


Best regards, Ingmar

Hello Ingmar,

I've send a copy of your latest post to the provider. Hopefully they can come up with a solution. I will let you know when they do.

Hello Ingmar,

My provider was able to resolve the issue, but still mentioned that the original problem is on your side, please see the following quote:

On the web server itself, we can now simply access vi-solutions.We couldn’t do this before because vi-solutions had indeed blocked 185.41.124.157.The outgoing IP has now been changed, which is why we can connect now.

As I understand correctly your website (server) is blocking the mentioned IP address, I can imagine that removing the block will also solve the issue with the reCaptcha. Because that is not yet solved, see this post .

Hello Jeron,

I was just on your productive site and Visforms is now actually working again in the update manager.

Thank you again for asking your provider.
Without his support and answer I would not have been able to find the cause on my own.
I am pleased that the update manager for Visforms is working again.

I am not aware of any blocking of individual IPs by our domain 'vi-solutions.de' or our provider.
I will investigate this matter with our provider as soon as possible and clarify this and other blockings.
At the moment I cannot explain what could have caused this blocking.

The following circumstance is a bit confusing:

Your provider speaks of the blocked IP 185.41.124.157.
However, scoutingalphen.nl was listed and accessible via IP 178.249.155.181 before the change by your provider.
Now scoutingalphen.nl has a different new IP 178.249.155.181.
But at least access to 'vi-solutions.de' works again, which is the main thing.

I'm still keeping an eye on the other open issue 'reCaptcha V2 is not validating'.
But I wanted to clarify this issue first because it was easier to handle and, according to my expectations, easier to solve.

Thanks for the info that it still doesn't work.
I'm clarifying IP blocks by our domain and our provider.
After that, I'll take care of the open issue 'reCaptcha V2 is not validating'.

Best regards, Ingmar

Hello Ingmar,

The IP 185.41.124.157 is part of the name server of my provider.
Update from the provider: They changed the outgoing IP address (likely to 178.249.155.181).