AiO 9020 EWS: HTTPS only works with IP address, but not the printer's domain name

[mcfisch]

I have an All-in-One HP 9020, that so far works fine. But its embedded web server gives me headaches: connecting through HTTPS works as expected when visiting via the printer's IP address, including the usual error due to the address not matching the name in the certificate.

But whenever I use any host name instead the website would not fully load and its scripted functions won't work either:

• The link to log in/out in the upper right always shows "Sign out", despite me not having logged in yet. Clicking it does cause the site to reload, but it remains unchanged.
• None of the functionality that requires the password will be available, the respective web pages only show the regular/static parts of the website

I've tried many different things yet nothing has helped so far:

• Different browsers (Chrome, Edge, Firefox, Safari) on different OS (Windows 11, Chrome OS, Android, MacOS)
• Original self-signed certificate as well as a valid certificate issued for my domain, uploaded into the EWS
• Different host names: the original name that is derived from the MAC address  as well as its own internal or external FQDN (i.e. print.mcfisch.lan or the external domain, DNS internally works)
• Changing name and domain of the printer
• Reset the printer to factory settings (this issue even occurs when nothing is yet configured other than Wi-Fi)
• Using a different password as well as removing it completely (without the password most of the pages are loading, but not all - and any functionality that usually requires a password is broken, causing all kinds of error messages)
• Updating the firmware (latest FW is from 2 days ago (Jun 30, 2022)

On some occasions the attempt to log out actually seemed to have worked as the lower right of the page had the blue button appear that says "Sign in". But when I click it I get the following error:

SyntaxError: Unexpected token o in JSON at position 1
    at JSON.parse (<anonymous>)
    at d.getAjaxPinCapability (https://print.mcfisch.lan/framework/Unified.js:103:5015)
    at Object.aM [as PromptCustomWIndow] (https://print.mcfisch.lan/framework/Unified.js:105:11920)
    at Object.complete (https://print.mcfisch.lan/framework/Unified.js:104:46509)
    at Z.ap (https://print.mcfisch.lan/framework/Unified.js:104:41552)
    at HTMLInputElement.<anonymous> (https://print.mcfisch.lan/framework/Unified.js:104:7429)
    at HTMLInputElement.handle (https://print.mcfisch.lan/framework/Unified.js:13:32652)
    at HTMLInputElement.<anonymous> (https://print.mcfisch.lan/framework/Unified.js:13:29495)

There either seems to be something wrong with the firmware of this model (but then more people should have reported this by now, right?), or something that isn't part of the replaced files is corrupted.

Can anyone please shed some light on this? I don't want to be condemned to have certificate errors just because I'm forced to connect by IP instead of a proper hostname...

Thanks

[Jim_WiFi]

Hello,

Thank you for the problem report, I managed to reproduce this once, although the condition appeared to clear after a sign-out, sign-in cycle.  Can you tell me the full Firmware Version string and built date show on https://printer-ip/#hId-pgProductUpdate

(Tools->Printer Updates->Firmware Updates)

Also does the same issue manifest if you try the mDNS/bonjour hostname?

found on https://printer-ip/#hId-pgBonjour 

(Network->Advanced->Bonjour)

For example:  https://HPHOSTNAME.local in a browser.  Or does this problem only manifest when using a traditional DNS FQDN

-Jim

[mcfisch]

Can you tell me the full Firmware Version string and built date show on https://printer-ip/#hId-pgProductUpdate

(Tools->Printer Updates->Firmware Updates)

Firmware Version: MANHHIPP1N005.2222A.00
Built Date: 2022-05-25

---

Also does the same issue manifest if you try the mDNS/bonjour hostname?

---

Apparently, this seems to happen only when using a regular DNS name. Connecting via Bonjour name does work the same as via IP address - functionally it is fine but obviously, the TLS certificate doesn't match.

BTW, I've configured the debug logs to be sent to a Syslog instance, and this is all that gets logged when I'm opening the web interface using a DNS FQDN and trying to sign out/in.

2022-07-05	09:26:17	Warning	print.mcfisch.lan	user	webserver	[webserver] OSPX TIMER_release(1871875) - handle 0xcafecafe001c9003
2022-07-05	09:26:17	Warning	print.mcfisch.lan	user	webserver	[webserver] OSPX TIMER_release(1839107) - handle 0xcafecafe001c1003
2022-07-05	09:26:05	Warning	print.mcfisch.lan	user	kernel	[229352.496652] ADDBA RSP: Failed(fc:XX:XX:XX:12:dc tid=6)

Singing out doesn't really work, and even when it seems it did - showing the 'Sign in' link at the top right - that link doesn't work, and the respective button at the bottom leads to the aforementioned JavaScript error.

Thanks