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

Partially Solved

While I haven't found a native solution on how to integrate NTFY to glance, I did build up something that actually send basic text streams to glance in an automated way. It's very rudimentary and probably error prone, but that's the best I could do right now... Maybe someone else will chime in and give some better advice/solution.

For those interested postgREST allows to build a simple docker container postgres database you can query for the custom api in glance. It DOES work, but If like myself, your database/json/postgre knowlege is very limited, it only allows basic text response like: "Update Failed".

I did try to get a little further into the rabbit hole, but it does come with the necessity to have a good database and query/response background ? Not a very good solution and will probably not go one or try to improve on that right now... But feel free to give better advice or another lead to foll

cross-posted from: https://lemmy.ml/post/26615546

The official docker image is still at v0.11 and was last updated in 2016. It looks like maybe trunk is at 0.12, but, as far as I can tell, that a rolling release. My prosody install is too important to go with a rolling release.

Both the alternatives that they point to are similarly old;

• v0.11.13 --- https://github.com/OpusVL/prosody-docker/
• v0.11.x (?) --- https://github.com/unclev/prosody-docker-extended

My server is langishing on the unclev image. I'd like to migrate to something with 0.12 and have a bit more confidence in its resiliance.

I'm routing game traffic on my VPS via wireguard to a home server that has games hosted via docker.

Setup is...

VPS/Wireguard -> Internet -> Wireguard/Dockerized Games Server

Now, my current config WORKS... however I'm curious if there is some unnecessary routing going on.

VPS iptable rules (omitted PostDown)

 undefined

        PostUp = iptables -t nat -A PREROUTING -i eth0 -p tcp --match multiport --dports 61000:61100 -j DNAT --to-destination 10.0.0.3
    PostUp = iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE



  

Game Server (omitted PostDown)

Here are the iptable rules on the game server and the --to-destination part is what I'm curious about...

 undefined

        PostUp = iptables -t nat -A PREROUTING -p tcp --dport 61000:61100 -d 10.0.0.3 -j DNAT --to-destination 192.168.1.14
    PostUp = iptables -t nat -A POSTROUTING -j MASQUERADE


  

10.0.0.3 is the same machine as 192.168.1.14

The reason I'm setting the --to-destination ip to that is because the docker rules that are created in the `Chain D

I have multiple things running through a reverse proxy and I've never had trouble accessing them until now. The two hospitals are part of the same company, so their network setup is probably identical.

Curiously, it's not that the sites can't be found, but instead my browser complains that it's not secure.

So I don't think it's a DNS problem, but I wonder what the hospital is doing to the data.

All I could come up with in my research is this article about various methods of intercepting traffic. https://blog.cloudflare.com/performing-preventing-ssl-stripping-a-plain-english-primer/

Since my domain name is one that requires https (.app), the browser doesn't allow me to bypass the warning.

Is this just some sort of super strict security rules at the hospital? I doubt they're doing anything malicious, but it makes me wonder.

Thanks!

Also, if you know of any good networking Lemmy communities

Hi guys I recently stumbled upon this website where you can get a eu.org sub domain (example.eu.org for instance).

I noticed though that domains aren't created instantly. I'm curious if there is human review to get domians processed and if it generally takes a long time to make domains using them.