Cloudmin Pro Documentation

SYSTEM INFORMATION
OS type and version Ubuntu Linux 22.04.5
Webmin version 2.401
Virtualmin version 7.30.8 Pro
Cloudmin version 9.8 Pro

Hi Everyone

I understand this has already been mentioned sometime ago (Cloudmin documentation topic)
But none of the referenced links I found seem to work:
https://www.virtualmin.com/documentation/cloudmin/
https://archive.virtualmin.com/documention/cloudmin/

Same happens when clicking on the Cloudmin documentation icon available at the Webmin System Information page

I guess I’m looking in the wrong place?
Any hint will be highly appreciated, thanks in advance!

All the best,

Eric

Hello Eric,

I still haven’t released the Cloudmin documentation. The work on WP Workbench took much more time than I originally expected.

@Joe, do you know why the old Cloudmin documentation site redirects to the shop?

I don’t know. It must be something on the new web server side, I think, as my redirect on the old archive server is to the exact same path on the newer server. If those links are broken, I don’t know.

This is where it should end up, I think:

https://www.virtualmin.com/documentation/cloudmin/

Which doesn’t work. Why doesn’t that work?

To be clear, all documentation paths on archive redirect (and should redirect) to the same path on the new server.

And, I believe it does that correctly:

$ curl https://archive.virtualmin.com/documentation/cloudmin/
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="https://www.virtualmin.com/documentation/cloudmin/">here</a>.</p>
</body></html>

The old archive link doesn’t work anymore—it used to, but now it just redirects to the main virtualmin.com site.

The new Cloudmin documentation hasn’t been released yet. I was thinking of putting it on www.cloudmin.com/docs, as it shouldn’t be on the Virtualmin site.

1 Like

I’m not opposed to new docs, it definitely needs an update, but in the meantime, we can’t just have Cloudmin docs be non-existent.

Archive isn’t supposed to work, it’s supposed to redirect to the same page on the new server. But, I guess the same pages don’t exist on the new server.

Yes, agreed. I remember we had the archive.virtualmin.com/documentation/cloudmin link working for years, but I think it recently started redirecting. I don’t remember making any changes, so I’m a bit confused.

Oh, that’s news to me. It worked for ages, and I had no idea it was going down…

I added the redirect a while back because archive links were consistently appearing above the new documentation in Google/DuckDuckGo/etc., and that’s extremely bad because those docs are unmaintained.

1 Like

Remember when I was yelling about documentation being poorly labeled (like searching for “restore” did not return any results), it was at that time when I was making the redirect…the only results for a search for “virtualmin restore” were on the old site.

But, the goal was to bring all the old docs over on their same URLs on the new server, and then update them as time allowed. Old URLs should work forever though. They shouldn’t change, if they do, there needs to be a redirect (but redirects are also suboptimal…ideally we’d have a URL at www.virtualmin.com/documentation that is forever).

Yes, and this is how I’ve set it up to be, for example:

https://www.virtualmin.com/documentation/tutorial/how-to-log-in

OK, but I don’t know what to do about Cloudmin docs.

For the time being, everyone should use the old documentation site from the archive:

Holy hell. No. That’s a terrible idea. I’ll figure out how to not redirect that, but we need Cloudmin docs on the new site.

All right, yeah, just don’t redirect Cloudmin docs part.

And, I can definitely finish up the Cloudmin docs—it’ll just take some time.

I know it will take some time though. I have to prioritize the new WP Workbench release and the next Virtualmin release, then we can look at the Cloudmin docs!

Good luck with that! Drupal is confusing! I fixed the Apache redirect, but I couldn’t figure out in a timely manner what the problem was with the Drupal redirects…