Hello,
I cannot connect to https://filezilla-project.org from our company with a browser (Chrome): Getting a timeout. Other browsers make no difference.
It's ok from my home, though. Hostname resolves to 49.12.121.47 at both places.
Wireshark capture shows "Destination unreachable, Port unreachable".
The company's firewall shouldn't block this and I couldn't find anything in the logs that it would. So my guess at this moment is that the project's firewall is blocking us.
Maybe triggered by several internal clients requesting updates? Is this possible?
Would prefer not to disclose our IP in the forum due to paranoia
Can provide it via DM.
Lars
Access blocked to filezilla-project.org?
Moderator: Project members
Re: Access blocked to filezilla-project.org?
Feel free to pm me your IP and I can have a look.
Almost definitely however it will be due to automated third-party software in your network that disregards robots.txt or HTTP 403.
Almost definitely however it will be due to automated third-party software in your network that disregards robots.txt or HTTP 403.
Re: Access blocked to filezilla-project.org?
Thank you for the private message. As suspected, you are using faulty third-party software.
I recommend using the built-in update mechanism of FileZilla, you can update as many machines as you like with it, there are no restrictions.
If you want to use a third-party product to deploy FileZilla within your network, you need to host the files yourself.
I recommend using the built-in update mechanism of FileZilla, you can update as many machines as you like with it, there are no restrictions.
If you want to use a third-party product to deploy FileZilla within your network, you need to host the files yourself.
Re: Access blocked to filezilla-project.org?
Could you please specify what is faulty there?
Then I can solve this with their support.
Then I can solve this with their support.
Re: Access blocked to filezilla-project.org?
Just log the network traffic to filezilla-project.org attempted by third-party products on your endpoints and get rid of those programs.