503 error on updating Advanced Module Manager

Hi Peter,
I am using your Advanced Module Manager since forever. It is crucial part of many of my websites, I am so used to it no matter what Joomla team does with modules control - you did it better.

Now, with some of the latest versions I noticed (not on all sites, so it must be something with server side, too) that I end up with 503 error when I click on automatic update for Advanced module manager.

"Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."


In Joomla, this is the report:

"Error connecting to the server: Failed to connect to 2a06:2ec0:ded1:1:0:48:671:1: Network is unreachable
Failed to download package. Download it and install manually from download.regularlabs.com/file.zip?ext=ad...core&file=update.zip ."

So I presumed it has something to do with update server, there's address:
download.regularlabs.com/updates.xml?e=a...ulemanager&type=.xml

Therefore, that address is correct and fine, but xml contains a lot of http://, not https://

I can check with system admin if there are issues with http being banned or something, but I suppose it's more default for you to change your links in xml with https, it's also what needs to be done, since you have all those set to secure level.

Can you confirm this might be the case and if you're going to change it and if not, why not, maybe there are reasons for http, not https... I know everything you do is far beyond precise and debugged! Congrats on that, thank you.

Meanwhile, I upgrade manually, everything works like a charm, of course.
Cheers!

Hi Peter, fast reply as always, thank you!

1 is not the issue, I have none of those installed on few sites on that server.
2 I'll check asap, but I doubt, no reason for blocking you and not other, much more "unsecure" devs
3 Please check 147.91.*.* IP if you have it the blacklist. It's academic network domain, very well administrated and protected, should not be problem either.

Thank you very much.

SOLVED!

I suggested admin to check IPv6 addresses availability on server and that was the problem, sice your server responds with IPv6 as stated above.
Thank you for your prompt response, maybe this thread helps someone else, too.

As for http vs. https in xml, that you won't change? I mean it works since it gets redirected to https anyway, but changing it in core sounds like perfection 🙂

Cheers, thnx!

Thank you!