[support] Siwat's Docker Repository

[Stuntard]

I'm not sure what is happening now. I can use dig @192.168.0.200 my.domain and it gives me the expected result (I have a DNS rewrite setup to change my domain name into my docker host's LAN IP (it's a different host machine than my Unraid Box).

 

But if I use a browser when connected via Wireguard, the websites time out. 

 

I had all this working before I updated Unraid so I don't know what has happened. I have Caddy setup to bypass auth if the connection is coming from a whitelisted LAN ip, which it should do, as the rewrite seems to work, but only from a shell, not my browser.

 

In fact, if i'm connected to my LAN via wireguard at all, I cannot access any of my machines via IP, apart from my Unraid box which is hosting Wireguard. As soon as I drop the wireguard connection, I can access things by IP again (I'm testing with my phone, but on Wi-Fi to LAN, and using Cell Data+Wireguard)

Edited April 8 by Stuntard

[xstefanx]

Is there a reason that the Homebridge UI is missing the options to "Remove Single Cached Accessory"? In the version that the docker is running, we should be able to access this setting from the Homebridge settings menu but the option isn't there. I've also tried updating the UI plugin and even when I get it to run the new UI for a restart or two it doesn't have the option either. (Side note that it would be nice if we had the option to either pull the most recent version of the UI or update it manually and not have the container override the version on boot)

 

Reason I'm after this setting is I have a few stale accessories that currently the only way I can find to get rid of them would be to clear the cachedaccessories file which would mean starting homebridge over from scratch. Not only would I have to set up the 40+ devices again, but all locations in home would be reset, and all automations involving these accessories would get wiped as well.

Edited May 1 by xstefanx

[Ikeasofa]

+ mysqladmin --defaults-extra-file=/etc/mysql/conf.d/client.cnf ping
mysqladmin: connect to server at '127.0.0.1' failed
error: 'Can't connect to MySQL server on '127.0.0.1:3306' (111)'
Check that mysqld is running on 127.0.0.1 and that the port is 3306.
You can check this by doing 'telnet 127.0.0.1 3306'
+ sleep 1

How do I fix this? Fresh installation with no changes to the template

[prubi]

Hello, i am new to the unraid community and setup my first home server with unraid. I would like to install to my server the onlyoffice community server suite to use it in my home lab- via docker. The installation is successfull, but when i visit the ip address/host where onlyoffice is installed i only see "The portal is starting up, it make take longer" and "Do not reload the page or shut down the pc". Thats all what i see, nothing more. Its stucked there. What can i do, someone help me with this please.

[thedinz]

Hello,

 

with only office is there anyway for me to change the port for mySQL as its conflicting with an other instance im running.

[thedinz]

On 5/1/2024 at 10:18 AM, Ikeasofa said:

+ mysqladmin --defaults-extra-file=/etc/mysql/conf.d/client.cnf ping
mysqladmin: connect to server at '127.0.0.1' failed
error: 'Can't connect to MySQL server on '127.0.0.1:3306' (111)'
Check that mysqld is running on 127.0.0.1 and that the port is 3306.
You can check this by doing 'telnet 127.0.0.1 3306'
+ sleep 1

How do I fix this? Fresh installation with no changes to the template

Same here but i am running another instance of mySQL and wondering if thats why the conflict