Wiki Publisher extention, User name or password is incorrect

Hi there,
I wanted to test the wiki publisher extention. I installed Ubuntu 20.04.3 LTS on Virtualbox and mediawiki 1.35.2. I can log without any issue on the Mediawiki page but when trying to configure a connection to my Mediawiki server from Libreoffice I receive “User name or password is incorrect. Please try again, or leave the fields blank for an anonymous connection.”
LibreOffice 6.4.7.2, Wiki Publisher extention 1.2.0.
I am using the localhost address 127.0.0.1
I cannot find any errors in the log, just the following trace in the apache2 access log

127.0.0.1 - - [03/Sep/2021:22:51:33 +0200] "GET /mediawiki/ HTTP/1.1" 301 609 "-" "LibreOffice Wiki Publisher 1.2.0"
127.0.0.1 - - [03/Sep/2021:22:51:33 +0200] "GET /mediawiki/index.php/Accueil HTTP/1.1" 200 17996 "-" "LibreOffice Wiki Publisher 1.2.0"
127.0.0.1 - - [03/Sep/2021:22:51:33 +0200] "GET /mediawiki/index.php?title=Special:Userlogin HTTP/1.1" 301 543 "-" "LibreOffice Wiki Publisher 1.2.0"
127.0.0.1 - - [03/Sep/2021:22:51:33 +0200] "GET /mediawiki/index.php/Sp%C3%A9cial:Connexion HTTP/1.1" 200 16280 "-" "LibreOffice Wiki Publisher 1.2.0"
127.0.0.1 - - [03/Sep/2021:22:51:33 +0200] "POST /mediawiki/index.php?title=Special:Userlogin&action=submitlogin HTTP/1.1" 200 16440 "-" "LibreOffice Wiki Publisher 1.2.0"

Any help welcome. Thanks

My default recommendation for all Ubuntu 20.04 systems with initial 6.4.7.2 Libreoffice installed from base repository before proceeding with any problem analysis:

  • dpkg --list | awk '/ii/&&/libreoffice/{print $2}' | sudo xargs apt purge --yes
  • sudo apt autoremove --yes
  • sudo apt install libreoffice libreoffice-gtk3 libreoffice-sdbc-hsqldb libreoffice-help-en-us --yes

(Complete re-installation, due to strange problems reported for this combination of distribution version and LibreOffice version, as there are: empty PDF exports, no text printed, incomplete menu bar, CUPS problems,…)

Of course, this does not guarantee that your problem is solved, but it guarantees that is not another issue adding to existing list of problem caused by some unknown problem in initial install.

Thanks Opaque,
Done but no joy. I don’t know how to debug this, very few traces. I wonder if the local host address is the issue.