w^w
Members
-
Joined
-
Last visited
Everything posted by w^w
-
It will be great to have this option
-
Hi @CorneliousJD. If you set openeats database collation to "utf8_general_ci" you can use "½ cup water".
-
@ljm42thanks for this detailed info about LAN-LAN config. Based on your work I successfully configured Server-Server feature. Have one question, is it necessary to have two different ports (52001 on unraid1 and 52002 on unraid2) instead one?
-
@bonienl thanks for this screenshoot but this is only configuration for "main server", could you post screenshoot about "backup server" settings? I'm asking about it because I'm struggling with this for many hours. I will be very grateful. Thank you.
-
Hi. I have exacly the same problem but when I put "intel_iommu=igfx_off" in syslinux.cfg file this error never shows up in log. But even if i don't use onboard Intel GPU when I pass my GeForce GT 1030 to any of my VMs unraid just hangs totally.
-
It's a very good information. Thanks
-
OK. Thanks for info.
-
Hi CorneliousJD. Since a Home Assistant have user authentication method is it possible to change the Appdaemon authentication from API password to something else (according to HA docs API authentication method will be dropped in next releases)?
-
Hi. I using GitLab-CE docker for all my company projects with these extra parameters: <ExtraParams>--env GITLAB_OMNIBUS_CONFIG="external_url 'https://subdomain.domain.duckdns.org/'; nginx['listen_port'] = 9080; nginx['listen_https'] = false"</ExtraParams> according to this post: https://forums.unraid.net/topic/48653-support-gitlab-ce/?page=3&tab=comments#comment-605797 In version 6.5.3 everything works fine but in version 6.6.0 and 6.6.1 I have an error trying to run gitlab docker: root@localhost:# logger 'docker command execution halted due to security violation (Bash command execution or redirection)' How to fix it? Please help.
-
It's working now. Thanks coppit.
-
Server and clients versions are OK. Clients (on windows computers and iphones) doesn't connect at all to the specified port: 8090. And I can't connect to the 10090 port via web browser. I run your docker from scratch and the problem with no connection still exists.
-
Hi coppit. I updated Xeoma docker to the newest version and after that I can't connect any client to the xeoma server. Logs are OK. here they are: Configuration: PASSWORD=<hidden> VERSION=latest 2018-08-16 09:18:00 Determining version of Xeoma to use 2018-08-16 09:18:00 Config version is "latest" 2018-08-16 09:18:00 Fetching version information from Felenasoft at http://felenasoft.com/xeoma/downloads/version2.xml 2018-08-16 09:18:01 Using Xeoma version 18.7.10 (the latest stable version) 2018-08-16 09:18:01 Downloaded file /config/downloads/xeoma_18.7.10.tgz already exists. Skipping download 2018-08-16 09:18:01 Installing Xeoma from /config/downloads/xeoma_18.7.10.tgz 2018-08-16 09:18:02 Installation complete [Aug 16 09:18:02] Setting the password Password set successfull Started runsvdir, PID is 56. Waiting for processes to start.... [Aug 16 09:18:02] Starting the server in 5 seconds. See the log directory in your config directory for server logs. run: cron: (pid 61) 5s run: xeoma: (pid 60) 5s My xeoma docker configuration is simple but I pass new port for xeoma web service.