After the URL renaming at Toolforge https://listpages.toolforge.org is no longer working. The Perl script at /listpages.pl results in the HTTP error 404. After copying the script to list_pages.pl it works again.
Summary:
https://listpages.toolforge.org/listpages.pl doesn't work
https://listpages.toolforge.org/list_pages.pl works
Both scripts are identical.
Hello. Is it the same problem for my tool WPCleaner, T257384 ?
The redirect removes the top directory in the path, breaking all the tools for each user as the tool can't update itself.
Mentioned in SAL (#wikimedia-cloud) [2020-07-08T16:22:17Z] <wm-bot> <root> Hard restart to correct webservice state tracking (T257417)
The hard restart seems to have fixed https://listpages.toolforge.org/listpages.pl. I'm pretty sure this was an instance of T254640: Default lighttpd config created by `webservice` breaks serving files starting with the same string as the tool's name under `--canonical`.
Please do the same "hard restart" for my other projects named "inactiveadmins" and "revertstat" (or even better: please do this for ALL tools of ALL users - I'm sure there are more of them affected).
@Aka Please do ssh into a Toolforge bastion and restart your tools yourself. I agree that in an ideal world we could magically fix this for everyone, but today we do not have the tooling to actually do that.
webservice stop followed by webservice --backend={kubernetes,gridengine} [type] start where the backend and the type are dependent on your tool. You can also make a $HOME/service.template file to hold the backend and type settings first. Then you can just do webservice stop; webservice start.