QuickScan for iOS now supports the Paperless-ngx API for immediate (and automatic) upload. 🙌

[john-work-ios]

Hi there,

It's been asked a lot by QuickScan users, and it's finally there: a proper API support for Paperless-ngx.
No more need for WebDAV or a SMB share to enjoy the automatic process & upload of QuickScan to Paperless-ngx.
... and 100% privately since QuickScan does not collect any data.

More info here : QuickScan website

Happy to answer to any question!

[shamoon]

Oh cool, is that your project?

[shamoon]

Im ready to make this my go-to scan app but one request: enable token authorization instead of u/p. My install (others Im sure?) is behind a reverse proxy and I allow API operations only with token auth.

Regardless, very cool!

[leutnantlurch]

Hey john-work-ios! Thank you very much for your app, it looks really great! But yeah, auth via API-token would be great, I use paperless-ngx behind authentik, so I can't provide a username or password. Keep up the good work! I will plan to use the app :)

[john-work-ios]

Thanks guys for the feedback, much appreciated! I will add a token field for authentication.
Cheers

[john-work-ios]

@shamoon @leutnantlurch, authentication via token is now available (I worked like a beast :D). Be sure to have the latest 7.7.1 update.

[shamoon]

Amazing! And so fast! Works like a treat too. Definitely just became my go-to scan app, appreciate you!

ps. There’s a tiny typo below the token field “passwor” 🙂

Cheers

[leutnantlurch]

Sorry for the late response but it is awesome! Fantastic support from your side, I will consider a donation 😃

[skeletoooooor]

Hey @john-work-ios
Thanks for the implementation. Unfortunately, I can't get it to work. I scan everything and set it up as export-favorite. No error. When I scan something, it says that it scanned it successfully, but the document doesn't appear in paperless-ngx.

Any info on what could be wrong?

[john-work-ios]

Tricky one! Well done :-). To be honest, I'm relieved that the origin of this issue is not in QuickScan :)

[skeletoooooor]

Danke @leutnantlurch für die ganzen Screens! Es läuft!
Thanks so much for the screenshots. Everything is working as expected.

Thanks @john-work-ios
Maybe that's something for the wiki. I had to restart the paperless container on my NAS after saving the token. Now, everything is working accordingly. Wonderful software! And most importantly 100% Private!!!!! Thanks so much.

[leutnantlurch]

Gerngeschehen @skeletoooooor 🥳

@john-work-ios Yeah maybe a wiki entry or a little hint at the config screen in the app maybe a nice idea?

[michelnet]

i have follow problem, my paperless just available over VPN and LAN behind a reverse proxy. with a let's encrypt certificate. My VPN solution is Wireguard. Back home everting works fine. When I connect over vpn, I can connect to the webpage. I receive follow error message:

Paperless-ngx-Fehler.
1 / 1 Dateien nicht übertragen General error. Code: -997
Domain = NSURLErrorDomain Description = Error
Domain=NSURLErrorDomain Code=-997 "Verbindung zum Hintergrundübertragungsdienst verloren" UserInfo={NSErrorFailingURLStringKey=https://domainname/api/documents/ post_document/, NSErrorFailingURLKey=https:// domainname/api/documents/ post_document/,
_NSURLErrorRelatedURLSessionTaskErrorKey=(
"BackgroundDataTask <61F25315-10D4-4FF8-B8D5-E3D9A6AC9BF6>.<1>",
"LocalDataTask <61F25315-10D4-4FF8-B8D5-E3D9A6AC9BF6>.<1>"
_NSURLErrorFailingURLSessionTaskErrorKey=BackgroundDa talask <61F25315-10D4-4FF8-B8D5-E3D9A6AC9BF6>.<1>,
NSLocalizedDescription=Verbindung zum Hintergrundübertragungsdienst verloren} 

[john-work-ios]

This is strange. Is the app in the foreground while you do this?

[florian-obradovic]

Oh this is awesome, thanks a lot for the hard work to everyone involved.

How is it possible to support client certificates?

I secure all my self hosted stuff with nginx reverse proxy and client certificate validation (nginx: ssl_verify_client on;).
So every client "pre-authenticates" with it's certificate, then the proxy passes to the app...
This works fine in Safari / any browser but not within QuickScan ( I get a HTTP error code 400 ).

[florian-obradovic]

The certificates are stored in the standard certificate store of the OS (keychain). When you open the URL via browser, you get a (default iOS/Safari) prompt to select a matching certificate (one that was signed by the root CA which is set on the server side).

You import it via mail, as pfx/p12 file, enroll (get a certificate) via MDM like Jamf/Intune/Mobile Iron, etc.

[john-work-ios]

I'd be happy to add this functionality, but there is no way that I would configure such a test environment (I'm really not into this kind of config).
Is there any way you could provide me with such environment?

[florian-obradovic]

Sure, how can I contact you privately?
I have everything setup:

• paperless-ngx instance running on docker (if you prefer another instance, let me know the public IP)
• nginx reverse proxy with ssl_verify_client on;
• account
• api token
• certificate (p12)

[john-work-ios]

I replied to your support email, maybe it landed in your spam folder.

[florian-obradovic]

You should've all you need in your mailbox now...

[john-work-ios]

Client-certificates are now supported for paperless-ngx, in QuickScan 8.1. Thanks to @florian-obradovic for his help on this!

[florian-obradovic]

thank you so much @john-work-ios.
This was an awesome collaboration experience. I love the simplicity of the user interface.

1. open certificate *.p12 file
2. enter password
3. works

Here an example NGINX Reverse Proxy Config: for SSL Client Certificate Validation:
https://gist.github.com/florian-obradovic/8e67c220370341b2c13ef85a142af685

[danilichti]

Hi, is there any chance of getting this to work with http + Tailscale?

[florian-obradovic]

Can you explain what that exactly means, please?
Tailscale just creates an overlay vpn so you can access paperless-ngx via it‘s IP / magicDNS name when you’re connected.

[danilichti]

The issue is, that QuickScan seems to require HTTPS. If I enter the Tailscale IP of my Synology + Paperless NGX Port, I receive the following error message.

[flotpg]

Ah ok - so then you must enable https. It should work with self-signed certificates or tailscale's https feature: https://tailscale.com/kb/1153/enabling-https

[danilichti]

That results in this error message:

[john-work-ios]

Hello,

due to iOS security restrictions, self-signed certificates will result in an error -1200 (the one you are having).
I'd suggest an actual valid certificate (Let's Encrypt for example).