BoKKeR

thanks I will do that, if you have a chance can you star the docker hub repo.

can you try adding a mounted config folder and reproduce the problem? -v /path/to/host/config:/config

I can look into this, can you share your docker run command that you get after adding the container?

I cant find this option, but to make sure I made a new container with a new config location and adjusted the config in swag, restarted swagger. I get the https login page on the subdomain, upon login I end up with the same error page.

Removing the block rebooting SWAG, I get even less access. I get to the login page. After login I am greeted with

thanks I tried that also. Same result I can resolve home assistant over nginx, but all the service calls fail.

I have multiple services running behind a reverse nginx proxy. But I am having issues with home assistant. The UI loads but the calls don't get forwarded and error out Failed to call service homeassistant/turn_off. Unable to find service light/turn_off I am running https://hub.docker.com/r/homeassistant/home-assistant on Unraid. This is the nginx config. The site loads but gives errors when I try to turn on lights. # make sure that your dns has a cname set for homeassistant and that your homeassistant container is not using a base url server { listen 443 ssl; listen [::]:443 ssl; server_name ha.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app homeassistant; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location /api/websocket { resolver 127.0.0.11 valid=30s; set $upstream_app homeassistant; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header Host $host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } } This is the command used to run the container: usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='HomeAssistant' --net='proxynet' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -p '8123:8123/tcp' --device='/dev/ttyUSB0' 'homeassistant/home-assistant' I am not sure if its more suited for home assistant?

Sounds great! The Version: 6.9.0-beta35 has this included ! yay!

Yes but its just bad, inconsistent UI

This is a small inconsistency in the UI. The dashboard docker dropdown includes the "Logs". The same dropdown in the Docker tab misses the Logs part, (as it at the end of the docker line as a separate button) Its just a small UI inconsistency but it tricks me every day.

+1 I would love to have this. Otherwise I might have to run a virtualisation OS and use that to run unraid

if you preset new like https://www.reddit.com/r/funny/new/.rss it should give you the newest submissions without the stickies. By default it uses top afaik. Does this work for you? @m0ngr31

Hey! sure I will look what I can do about it!

Overview: Support for Docker image RSSTT in the bokker/rss.to.telegram repo. Application: RSS-To-Telegram - http://deluge-torrent.org/ Docker Hub: https://hub.docker.com/r/bokker/rss.to.telegram GitHub: https://github.com/BoKKeR/RSS-to-Telegram-Bot PS: Icon was made in PS under 10 minutes

How would I test out if my XML works as intended without submitting? Also how would I submit it? Where do I host the XML? Much of this information is hard to find as the documentation is scattered across multiple threads in multiple categories. Would be so much better if this info would be hosted in the plugin itself on its own page, "How to publish".

I have had the same issue, but I solved it by enabling windows time sync on startup. services->windows time->automatic

If anyone is using the USB Hot Plug for VM's with no passthrough, the modified version, the ignore list items need to have the lsusb device ids, not device names!

Same issue, some shares connect some dont. its really frustrating. Tried [default] port445=both signing_required=no smb_neg=normal in /etc/nsmb.conf on my mac and rebooting. didnt help

Sorry to bring this thread back up, but I still cant figure this out. Which way is the proper way?

It would be nice to have the option to remember the logged in root user sessions in the WebUI just like the forum can remember our credentials. The current behaviour is that the sessions get cleared after rebooting. Which can result in multiple logins a day per device, when thinkering with unraid. This can be considered a security issue but its down to the users how they use it.

Everything has been working wonderfully. With most of the configs for different linux-server containers its really easy to setup. But I ran into a issue when I wanted to set a reverse proxy for a webdav docker container. The issue is that the container runs on port 80 internally! if I add it to proxynet it will crash with letsencrypts port 80. Only way I see to fix this is by changing the port internally in the container. But I dont see that being possible without rebuilding the container https://hub.docker.com/r/bytemark/webdav/

I am having problems with the iw4x container, the game server runs fine about 3-5 minutes than crashes every tiem. because of some internal command failing https://pastebin.com/EYpWYA5N I have included the full log but the crash is at: 0009:err:winediag:nodrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly. 0009:fixme:dbghelp:elf_search_auxv can't find symbol in module 0009:fixme:dbghelp:MiniDumpWriteDump NIY MiniDumpWithHandleData 0009:fixme:dbghelp:MiniDumpWriteDump NIY MiniDumpScanMemory wine: Unhandled page fault on read access to 0BCC5F08 at address 006B5FE0 (thread 0009), starting debugger... Can't attach process 0008: error 5

In the first post IW4x (CoD:MW3 Mod Server), it should be MW2

most of these RGB contollers on these motherboards/rams/gpus are proprietary and they differ between models from the same manufacturer often. So there is little to no initiative for anyone to write plugins/containers for these things. Most have hardly any control from linux to begin with. Your best bet would be to boot into windows to give the system direct acces and turn them off. Only way to change any of these easily is to pass them into a windows vm, like a gpu and there you can use the utilities the manufacturer provides

yeah! My bad, I thought this was a general help thread. Thanks anyway!