u/DikkieDick1967

Hi, I'm running Nextcloud behind a reversed proxy (Zoraxy). That is running fine. And until recently also the built-in CODE was working fine. This morning I wanted to edit a document and got the message that it failed. Then gave it a try with the external Collabora-docker-container and alltough the WOPI-allowlist is set to 0.0.0.0/0 Collabora complains:

wsd-00001-00019 2026-09-15 09:11:24.317443 [ websrv_poll ] DBG  convert-to: Requesting address is denied: 1.2.3.4|home/collabora/jenkins/workspace/package_code_26.04_rpm/rpmbuild/BUILD/coolwsd-26.04.3.1/wsd/ClientRequestDispatcher.cpp:463

whereas 1.2.3.4 is obviously the ip-address I'm connected with.

Where can I look into this further? As this is really bothering me now. No changes have been made recently to the containers.

Can't find it. Am using the same WEBPASSWORD for years but seems it has now been renamed to FTLCONF_webserver_api_password, so added the same password in the value for that environment variable. Starting up the docker container doesn't show that it has set a temporary password so trying to login locally using my ip-address:8123/admin and enter this password but it's not recognized. I can reset it by pihole resetpassword. Well not anymore after setting FTLCONF_webserver_api_password it seems, but before I had set that I could. pwhash stays naturally the same and I have /etc/pihole on a persistent volume.

No the GUI can't be accessed and in my HomeAssistant. My pihole-integration is also showing unreachable. A bit later: I found that I had to re-authenticate so entered my password there and in HomeAssistant I'm getting the information again.

How to solve the GUI-issue? Have looked and looked but can't seem to find it.

Hi, I have a Rose PRO 105 SL Disc from 2023 which has Rose Twentyfive wheels with currently Continental 28mm tyres. I'm trying to find out what the maximum tyrewidth of the wheel is but can't seem to find out.
I'm getting a new bike (no Rose) soon and want to keep the Rose as backup but modify it to use it for gravel rides so a bit wider tyres would be nice.
Thanx in advance.

I'm running Nextcloud and Collabora in 2 Dockercontainers and everytime my ip-address at home (due to f.e. a power disruption) I won't be able to edit documents. Previous times I found that editing coolwsd.xml sometimes solves it, but today I can't get it working. I'm not using the builtin-code-server as that one isn't and wasn't also working. Nextcloud can connect to my own collabora-server, and I have put the new ip-address in wopi-allowedlist but still without success. Also in Cloudflare I whitelisted the new ip-address.

Is there a more easy way to solve this no matter if the ip-address changes in the future? As it's costing me everytime a few hours to dig and solve, even when I remember what the solution for last time was.

Both are behind Zoraxy reverse proxy. And if I enter collabora.mydomain.com in the webbrowser it gives an OK.

Update: solved. I had to modify config.php in nextcloud to add my ip-address to the trusted proxies. And also added collabora.mydomain.nl to trusted_domains.

I'm following what is described in the archived thread https://www.reddit.com/r/homeassistant/comments/1nu0bhg/honeywell_lyric_home_thermostat_t5t6_integration/ but no matter what I do in HA it won't show up when I want to add a HomeKit device. And as it seems the old integration stopped working (ssl-certificate-expired-message) and unable to logon to the developer dashboard at Honeywell complaining about bad email/pw-combination whereas I can login in the Residio-app I'm totally lost with this. Been trying this now for a few hours without succes.

Anyone more recent experience?

All of a sudden my password which I have been using for years isn't working anymore. I was running the docker container with 2026.4.0. Also updated to 2026.4.1 in the meantime without success.
If I do pihole setpassword and leave it blank I'm able to. I also set a brand new password, put it as environment variable in the stack without success. And I am using the correct password.

Removing the password gives me a temporary random password. If I fetch that from the logs it's also not working. Then I set a new password, try to logon without success.

Any clues?

Bit later: solved, had to create en entry in my hostsfile pointing to the localip of the pihole-instance. Now it's working.