Thanks a lot. You saved my lifelezerogan2 wrote:update:
instead of http://totalcmd.net/ i put https://totalcmd.net/
and now it is ok
![Very Happy :D](./images/smilies/icon_biggrin.gif)
Are there any news regarding the website? Will the regular (HTTP) site be up soon?
Moderators: white, Hacker, petermad, Stefan2
Thanks a lot. You saved my lifelezerogan2 wrote:update:
instead of http://totalcmd.net/ i put https://totalcmd.net/
and now it is ok
Code: Select all
109.237.110.23 totalcmd.net www.totalcmd.net
Just tried it - it makes Total Updater able to connect to totalcmd.net again. But mind that Total Updater's database is not maintained anymore, so plugins that are not placed on the internet where they used to be will no longer be found, and I doubt that newly introduced plugins on totalcmd.net can be found,Do you know if this also affects Total Updater?
GreatTU should use special requests to totalcmd.net which I had implemented specifically for it. Therefore it should obtain the actual list of plugins without any need of manual maintaining.
Code: Select all
109.237.110.23 totalcmd.net www.totalcmd.net
Flint wrote:Hurdet
Unfortunately the RSS is a statically generated file, and I don't know how to provide universal HTTP/HTTPS links in it. The standard trick with replacing http:// with just // to use the current protocol did not work.
Single slash means path on the current domain; double slash means another domain at the same protocol. For example, if you opennsp wrote:You could probably replace http:// just by / do not double it !
I already explained, http or https has nothing to do with it. It's just so happenned that your browser decided to use one IP when connecting to http, and another IP for https. It could have been the reverse, and you'd have working http and non-working https. Or both working. Or noth not working. Or working randomly, when hitting F5 gives you either 404 or the correct page. It's all due to the fact that one of the IP addresses returned by the resolving does not work. As I wrote above, I already removed it from the name server configuration, and it should already work OK. If it doesn't check what the command "nslookup totalcmd.net" returns, maybe your DNS server did not update the information yet.nsp wrote:Will you fix http ? as for now, even if it works correctly for https, http protocol have some issues.
"404 Not Found"