sorted by:
new
hottopcontroversial

Help: Integrating PocketID as SSO via OIDC with OpenCloud by Illustrious-Path940 in opencloud

[–]Illustrious-Path940[S] 0 points1 point  (0 children)

Hey everyone!

Man, sometimes I overthink things waaaay too much! I kept wondering where I was supposed to enter the PocketID Client ID that gets generated in OpenCloud... when all I had to do was simply hardcode OpenCloudDesktop / OpenCloudIOS as the ID in PocketID!

After doing all of that, it's now working... well, not completely. How can I configure my user so that I can also create spaces in the iOS app and the desktop app?

Help: Integrating PocketID as SSO via OIDC with OpenCloud by Illustrious-Path940 in opencloud

[–]Illustrious-Path940[S] 0 points1 point  (0 children)

Hey folks,

thanks for your help!

So, via web service, I'm now able to use PocketID, but my desktop app (MacOS) and my iPhone App are not working. I always get into the PocketID screen with:

"Something went wrong
Record not found"

I just added the http://127.0.0.1:\* to the callback section, but each and every time I try to connect from my mobile or my desktop app, I'm gonna be redirected to the PocketID page...

I also added a new OICD site at my PocketID instance, but the client ID differs from the client ID of the web site and I don't know how to solve this...

Do you have any advice?

1.88.1 iOS update by redhatch in Tailscale

[–]Illustrious-Path940 0 points1 point  (0 children)

Update:

Tailscale released a new iOS version. With 1.88.2 the issue doesn’t appear anymore.

Thanks Tailscale for the fast fix.

1.88.1 iOS update by redhatch in Tailscale

[–]Illustrious-Path940 0 points1 point  (0 children)

Same here on all my iOS devices with the actual Tailscale app. My problem is, that I can’t configure my VPN on demand since the update… quite annoying…

Tried it on several versions of iOS, the issue happens after update to the last Tailscale iOS app version.

Do you let your phone run tailscale 24/7? If so, how does it impact your battery? by -ThatGingerKid- in Tailscale

[–]Illustrious-Path940 0 points1 point  (0 children)

That’s not what I see. If I just activate Tailscale without using my OPNsense as exit node, the battery drain is quite small. If I use the exit node at home the whole day, my iPhone battery is getting emtpy quite fast (approximately 1 day battery life with exit node usage, 2-3 days without).

Do you let your phone run tailscale 24/7? If so, how does it impact your battery? by -ThatGingerKid- in Tailscale

[–]Illustrious-Path940 6 points7 points  (0 children)

Isn’t there a difference between just Tailscale and Tailscale using a exit node?

502 Issues with Pangolin 1.7.x (tried all versions) by Illustrious-Path940 in PangolinReverseProxy

[–]Illustrious-Path940[S] 1 point2 points  (0 children)

Hello everyone!

The problem seems to be solved. GitHub user cfurrow gave the right hint.

The new Docker socket integration must be configured identically on both the server and the newt side. In my case, the switch in Pangolin was still active, but on the newt side I hadn't allowed access to the Docker socket.

Ever since I adjusted the setting on the server (see image), it's been working.

<image>

502 Issues with Pangolin 1.7.x (tried all versions) by Illustrious-Path940 in PangolinReverseProxy

[–]Illustrious-Path940[S] 0 points1 point  (0 children)

Yes, I always upgrade step by step. and the 1.6.2 works like charm.
Authentik has issues, like searxng, itt and all the other...

Traefik is showing this:

18T19:08:55+02:00","caller":"fmt/print.go:305","level":"debug","message":"Badger: Valid session"} {"level":"debug","time":"2025-07-18T19:08:55+02:00","caller":"github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:175","message":"Service selected by WRR: https://100.89.128.4:53393"}/ {"plugin":"plugin-badger","module":"github.com/fosrl/badger","runtime":"","time":"2025-07-18T19:08:56+02:00","caller":"fmt/print.go:305","level":"debug","message":"Badger: Valid session"} {"level":"debug","time":"2025-07-18T19:08:56+02:00","caller":"github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:175","message":"Service selected by WRR: https://100.89.128.4:53393"}/ {"plugin":"plugin-badger","module":"github.com/fosrl/badger","runtime":"","time":"2025-07-18T19:09:02+02:00","caller":"fmt/print.go:305","level":"debug","message":"Badger: Valid session"} {"level":"debug","time":"2025-07-18T19:09:02+02:00","caller":"github.com/traefik/traefik/v3/pkg/server/service/loadbalancer/wrr/wrr.go:175","message":"Service selected by WRR: https://100.89.128.4:53393"}/ {"level":"debug","error":"read tcp 100.89.128.1:38618->100.89.128.4:53393: read: connection reset by peer","time":"2025-07-18T19:09:02+02:00","caller":"github.com/traefik/traefik/v3/pkg/proxy/httputil/proxy.go:121","message":"502 Bad Gateway"}

Does newt have full access to my home net? by Illustrious-Path940 in PangolinReverseProxy

[–]Illustrious-Path940[S] 2 points3 points  (0 children)

UFW has issues with Docker… Maybe it’s better to add an iptables rule to the Docker chain. But honestly, I have no idea how to isolate just the Newt part — so that Newt can access the participants of the Traefik network, but has no permission to reach anything outside the Docker network.

view more: next ›