kreene1987

Has anyone got gog working successfully in the dashboard? I've got oauth credentials loaded, in CLI the auth is valid and I can give commands to get upcoming schedule items and recent emails, but as soon as I move into dashboard it presents errors. I've found this but I'm just a casual code enthusiast and don't really understand what all I need to do to get this to work: https://www.reddit.com/r/openclaw/comments/1saifdm/openclaw_gog_fails_on_headless_linux_with_keyring/?solution=96a35ee98caf4a1696a35ee98caf4a16&js_challenge=1&token=bbbe4bf1c9a2b5160829c4be34da5861b073059f2681f53e3d9bd51d86b8f2b3&jsc_orig_r= I have confirmed credentials are within /appdata/openclaw/config/gogcli/credentials.json, along with keyring folder which has valid gogcli_key_v1_... files. gog auth list --check returns my email with oath gog auth doctor --check returns no errors AI is telling me to add variables for the docker, but so far nothing has worked. AI is saying: The gog tool is still reporting missing OAuth client credentials. This indicates that the authorization step, where the user provides their Google credentials to the gog tool, has not been successfully completed or is not being recognized by the tool. I have already provided instructions twice. The error message is very specific about needing a downloaded JSON file and running gog auth credentials <credentials.json>. It also specifies the expected location for this file (/root/.config/gogcli/credentials.json).

I am having this issue on 6.10 stable on my R510. edit: fixed extra space in first try and now I am up and running... phew!

yeah I'm out of it today. Sorry.

I've thrown a recommendation in the upgrade notes that people change their ports away from 443 and 80 due to the conflict with the new Unraid SSL cert system. Perhaps that will alleviate a lot of the common issues seen above.

Glad to see this implemented! I think it will work great.

Yes thank you so much binhex. I'll let you guys know if any further mail shows up, but for now everything seems to be working as expected. Lesson learned: USE the privoxy for your meta gathering apps!

I've now incorporated socks5 with auth proxy for all 4 levels

See responses above. Thanks for responding so quickly. I suspect the socks might be the issue?

So I just got a nastygram from my ISP, and I'm wondering how in the heck it happened. I shut it down for now but plan to bring this back online. I've confirmed my IP and DNS are not leaking via ipleak, I am getting a good VPN connection per the logs, and I've confirmed via magnet link from ipleak that my external IP matches the logs. Is there anything else that I can do to test for leaks? I'm not entirely sure how it happened. Is there any way to add a killswitch or is this already a part of the build? Wanting to be as safe as possible considering the circumstances. TIA.

Me either. I will state that I am using www.domain.com/nextcloud settings, so I'm unsure if this is because I went with a bit different approach?

Phew this one is throwing me for a loop. I port forwarded my IP 80 --> 81 and now I can VPN in and get to all of my internal links and everything is working great, but the Unraid GUI connection is refused. Any reason the 2 would be related?

I hope someone sees this soon as I basically live out of nextcloud (calendar, documents, etc.) and this has brought this to a screeching halt without VPN'ing into my network! Is there a way to roll back to a previous revision?

Mine is dead this morning as well. Same error log as above with different webserver address (clearly).

I am getting a notification that 12.0.2 is ready for installation, is this something I should wait for the docker to be updated or is it ok to update within the software? Usually I like to hold for a docker update.