ZeusBfd

Members
  • Posts

    6
  • Joined

  • Last visited

ZeusBfd's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Every time I restart the docker I get activation problem message and have to reactivate to get it working. is there a fix for this?
  2. That seems to have fixed it. For some reason on first boot it put my NAS IP 192.168.1.200 in the my.service.xml file. I've edited it to 127.0.0.1 and all is well. Thank you so much for your help. Much appreciated.
  3. Yeah still no joy, says connecting... for about 30sec then unable to connect. 4243,550b1e37-a1e4-4acc-9472-553f128af5c0,127.0.0.1 then when restarted 4243,677087fb-bbf3-4e28-843c-7dd6963cbc3a,192.168.1.200
  4. My settings show as follows: Network Mode : NAT Host Container Protocol (blank) 4243 TCP 5901 5900 TCP 5800 5800 TCP
  5. Just would like to thank Djoss for this amazing container. I do have a slight issue tho. Upon setting up the container everything works fine. its only when the container is restarted things go a little side ways. When I restart I get the engine not found message, and I also notice the ui_info file changes. I've tried giving the ui_info file read only permission but still get the same results when restarted. 4243,aa19c4d7-36c9-4dfc-af04-01f51fc1cb99,127.0.0.1 (works fine) then when restarted 4243,81f08a16-6c87-4efb-91ad-ee53df01c8cb,192.168.1.200 (doesn't work and IP changes to my NAS IP) Can you help? Im using QNAP Nas btw