Problem accessing ScannerCapabilities on EPSON ET-2650 via http

[kjabl]

Describe the bug
I get a 404 "Fehler beim Abrufen der Eigenschaften des Scanners: NotSuccessfulCode(responseCode=404)

To Reproduce
Steps to reproduce the behavior:

1. Go to the App on the Screen "Scannersuche"
2. Click on your Scanner
3. See error

Expected behavior
I'm not sure what would be the next step, but I guess some screen to start scanning.

Screenshots
If applicable, add screenshots to help explain your problem.

Smartphone (please complete the following information):

• Device: Google Pixel 8a
• Android version: [e.g. 14]
• ScanBridge version: 1.1.0 (1001000, 60a14e7)

Additional context
I have an Epson ET-2650. It is shown on the search screen als
"EPSON ET-2650 Series-0BF096-03"
http://192.168.178.9.170/eSCL

When I tried to load http://192.168.9.170/eSCL/ScannerCapabilities in the browser on my laptop I get the 404, too. But via https it works. Sadly the scanner doesn't seem to advertise itself as https.
I just found out I can manually add a scanner. That way I can force SSL but the app doesn't accept my scanners self signed certificate.
Is there any way to circumvent this without creating an own root CA, new certificate and loading that certificate into scanner and root CA into the device?

[Chrisimx]

Can please install the latest nightly build? Test with this version whether it works. There were a lot of changes in this direction, so it might be possible that this is fixed already. But if your scanner really only has an HTTPS endpoint for eSCL it would be necessary to either create a root CA (and adding it in the Android settings) or, and this is in my opinion much more user-friendly, make it possible to add exceptions for specific cert and hostname combinations.

It would be interesting to see how your scanner service info looks like. For this you have to go into the settings and activate the debug log checkbox. Then try to connect to your scanner in the discovery screen. Finally, go into settings again and export the debug log to a file.

You can either upload the file here or send it to [email protected]. If the connection to your scanner would work, the file might contain the serial number of your scanner. If it can't connect it might only contain an UUID which I'm not sure of whether it is unique to the device or whether it would change if you'd reset the device.
Anyway, if you want to censor it, you can search for "UUID=" in the file and replace that UUID. You can also search for "scan:UUID" and "pwg:SerialNumber" in the file but if it can't connect these strings should not be found there.

[kjabl]

Hi @Chrisimx thanks for your quick response! I'm sorry it took me so long to test again.
I just tested with the latest nightly build from today (february 11).
It took me a few attempts today. At first I got timeout then 503's.
But now it works absolutely fine.
Even with the http version. I don't know what happened but now my Scanner answers on the http requests. Also from the computer. The https still gives me the self signed certificate error but that's no problem anymore.

Thanks alot. I think your app is great.

[Chrisimx]

Thank you! ❤️