fileburst.com down, no access to certain TC plugins

[Robbie]

Hi

I noticed that some plugins cannot be downloaded since they are hosted from FileBurst while this site is down.
Are any alternative sites available and should the Total Commander Plugins site be corrected for this?

Kind Regards
Rob

[Dalai]

No problem here whatsoever.

[Robbie]

Hi All

3 checks, all fail:

1)
https://plugins.ghisler.com/plugins/iso_plugin.zip in Chrome, gives:
ERR_CONNECTION_TIMED_OUT

2)
Ping in CMD gives:
Microsoft Windows [Version 10.0.19045.3803]

>ping www.fileburst.com

Pinging www.fileburst.com [52.15.96.207] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 52.15.96.207:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

3)
https://www.isitdownrightnow.com/fileburst.com.html gives:

[DOWN] Fileburst.com is DOWN for everyone.
It is not just you. The server is not responding...

Kind regards
rob

[Dalai]

I can download the file you linked without any problems. Something is blocking access on your client; could be a firewall on your client, perhaps part of an "internet security" software, or it could be your router. Try a different browser or try to download with a different system.

---

plugins.ghisler.com is not the same as fileburst.com which might not be the same as www.fileburst.com.

Apart from that it's possible that servers don't respond to an echo request (aka ping). But plugins.ghisler.com does answer them for me:

Code: Select all

C:\>ping plugins.ghisler.com

Ping wird ausgeführt für http.fileburst.com [205.251.73.100] mit 32 Bytes Daten:
Antwort von 205.251.73.100: Bytes=32 Zeit=167ms TTL=55
Antwort von 205.251.73.100: Bytes=32 Zeit=136ms TTL=55
Antwort von 205.251.73.100: Bytes=32 Zeit=138ms TTL=55
Antwort von 205.251.73.100: Bytes=32 Zeit=136ms TTL=55

Ping-Statistik für 205.251.73.100:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 136ms, Maximum = 167ms, Mittelwert = 144ms

Code: Select all

root@fli4l-router:/ # ping -c 4 plugins.ghisler.com
PING plugins.ghisler.com (205.251.73.100): 56 data bytes
64 bytes from 205.251.73.100: seq=0 ttl=56 time=235.630 ms
64 bytes from 205.251.73.100: seq=1 ttl=56 time=248.105 ms
64 bytes from 205.251.73.100: seq=2 ttl=56 time=268.985 ms
64 bytes from 205.251.73.100: seq=3 ttl=56 time=273.281 ms

--- plugins.ghisler.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 235.630/256.500/273.281 ms

Responding to a ping only means that there is some server responding. It doesn't necessarily mean that there's a web server, or even an accessible web server. What I'm trying to say is that testing a ping doesn't give any insight if a web server can deliver data to a client.

Regards
Dalai

[JOUBE]

No problem here whatsoever.

Same: No problem here whatsoever.