Webmin Servers Index

[ai-hosting]

When using Webmin Servers Index to navigate to other servers the link for virtualmin is not working. The url is linking to the main server and not to the remote server.

[iliajie]

Could you please attatch a screenshot to make it more clear?

[ai-hosting]

The first screenshot is taken after clicking one of the server links in Webmin Server Index so far so good (https://domain.tld/servers/link.cgi/123456789). In the Webmin tab everything is working. Url still
contains the 123456789 referring to the corresponding server. When clicking the Virtualmin tab 123456789 disappears and loading halts. In my case because the server used to connect to the remote server doesn't have virtualmin. The remote server does have virtualmin installed only the url reffering to the remote server is gone.

[ai-hosting]

[iliajie]

Does it happen with Link type Login via Webmin with username? What should be happening as you think? Because I opened Virtualmin Framed Theme and I came across the same behavior as in my theme. What happens if you go to Module Config and set Show servers as: Table?

When clicking the Virtualmin tab 123456789

Not sure how to get there? Could you please explain?

[ai-hosting]

To test you need to login in Webmin at server 1 and connect to server 2 with webmin module servers index. As soon you use virtualmin the theme loads the virtualmin module at server 1 instead of server 2.

123456789 is an example. In my case (screenshot) the number is 1357987894. This number is reffering to cloud1 in my case. The number is generated by webmin servers index.

[ai-hosting]

this only happens in authentic-theme. Gray frame, caldera, bootstrap 3, MSC themes tested without any issues.

[iliajie]

I will test it a bit later and let you know what I got.

[iliajie]

Confirmed! I see the reason why it's happening but..

..it will take a while to fix it though, as I will stay busy for future weeks with urgent work.

I will pile up upcoming issues and fix it whenever I can find time for it.

[iliajie]

It will be fixed in version 11.10 shortly. Thanks for reporting!