Selfhosted

49500 readers

886 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

[Question] How to re-authenticate a paperless-ngx oauth2 mail configuration (lemmy.world)

submitted 1 month ago by urandom@lemmy.world to c/selfhosted@lemmy.world

1 comments fedilink hide all child comments

Hi,

I've been been happily running paperless for a while now, and I've even got a few useful mail actions. However, I'm having trouble keeping the oauth2 (gmail) configuration alive past a few weeks. I suspect the refresh token expires, since the configuration stops working. And since I can't figure out how to re-authenticate, I have to create a new configuration, move all actions to the new one, and delete the old one.

Does anyone know how I can keep the original config and just re-authenticate?

Thanks

you are viewing a single comment's thread
view the rest of the comments

[–] catloaf@lemm.ee 4 points 1 month ago

I'm not familiar with paperless-ngx, but it should really be doing this on its own. If it doesn't, and you're not able to edit the config, you should probably open a bug report.

If you're just using this to send mail to yourself, though, you can work around it by sending direct to Gmail with unauthenticated SMTP. I have this configured on a couple systems. You might need to hit "not spam" on the messages a couple times because they'll probably get flagged at first.