If you run docker-compose ps, it will list the name of the running containers.
Find the one with cms-web in the name.
Then with that name, run
docker exec -ti name bash
That will open a console inside the container. From there, can you run:
wget http://url/of/your/rss
What do you get?
OK. You can type exit to get out of that terminal.
I suspect it’s the following:
https://robinwinslow.uk/2016/06/23/fix-docker-networking-dns/
Try making the change under the Update the Docker daemon section, and then
docker-compose down
docker-compose up -d
IM getting another error while trying to bring teh container back up now, and the error stays if i remove the daemon.json file and try and start it again.
ERROR: Couldn’t connect to Docker daemon at http+docker://localunixsocket - is it running?
If it’s at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
Sounds as if the docker daemon isn’t running.
Did you get an error when you restarted it?
cancel that, that problem has gone after a restart, i think it.I just confused with permissions somewhere with writing to teh system files, restarted the vm and the container started fine
This is what the log is saying since its started up again, I dont know if it has anythign to do with it…
2129 25c3f95 2017-04-06 14:54 CONSOLE GET ALERT / Layout has empty region
2128 898fd09 2017-04-06 14:53 CONSOLE GET ERROR /1 Unable to Process Queue of Player actions due to 2 of 2 player actions failed
2127 898fd09 2017-04-06 14:53 CONSOLE GET ERROR /1 Player action connection failed. E = XMR connection failed. Error = Failed to connect the ZMQ: Protocol not supported
2126 898fd09 2017-04-06 14:53 CONSOLE GET ERROR /1 Player action connection failed. E = XMR connection failed. Error = Failed to connect the ZMQ: Protocol not supported
In the CMS settings, what are your XMR public and private addresses set to?
Still get the same error for the wget command.
Priviate - tcp:://localhost:5555
Public - tcp:://localhost:5556
Private should be
tcp://xmr:50001
Public should be the DNS name or IP address that you access the CMS at (as the Player sees it)
tcp://name:9505
You definitely downed the container and recreated since the reboot? The correct DNS server IP for your network is in the json file now?
the container was down when i rebooted, i couldn’t get it back up, that’s why i re booted.
I’ve put those address is but I’m still getting the operation timeout.
what link did you try please?
What exactly do have now in XMR public and private addresses?
Priviate is - tcp://xmr:50001
And public is tcp://10.2.200.254:9505
Did you try to fix that DNS issue as described in that post?
If you mean by creating the daemon.json file with my dns server in it then yes I did
I can get the container to start again now, same error as earlier
Ok, fixed that one again, service didn’t start for some reason
So what’s the state now? Is nslookup working or not?
No, still not working this morning