Question related to pvoutput-integration-service / pvoutput.org

[NuShrike]

For what its worth, the "no route to host" means that the docker container's network isn't able to navigate to the PW. If you can get to it from your network via your browser, that implies to me that it is just the docker container that can't get there, which would make a lot of sense if your docker container isn't configured properly. Docker containers don't necessarily share the hosts network...they can be their own isolated network.

When you are in the Docker app on the Synology...can you click on the container area, click details on the container, and then let me know what your network tab shows? Is it in "bridge" mode?

No, he's already having this problem from the Synology host. Beginning of the thread.

 

[dotbombjoe]

No, he's already having this problem from the Synology host. Beginning of the thread.

Got it, yeah, that is odd -- for the synology to not be able to see the PW but his computer can. If the NAS and the computer are on the same network, I can't really make any sense of that. I'd be curious to see the output from the following command on both his computer and the synology: netstat -nr

 

[Story]

For what its worth, the "no route to host" means that the docker container's network isn't able to navigate to the PW. If you can get to it from your network via your browser, that implies to me that it is just the docker container that can't get there, which would make a lot of sense if your docker container isn't configured properly. Docker containers don't necessarily share the hosts network...they can be their own isolated network.

When you are in the Docker app on the Synology...can you click on the container area, click details on the container, and then let me know what your network tab shows? Is it in "bridge" mode?

Thanks -- the container has no network connections added specifically, but the overall container is in Bridge mode, yes.

What network connections should I add to enable https out from the container to the network?

 

[Story]

Got it, yeah, that is odd -- for the synology to not be able to see the PW but his computer can. If the NAS and the computer are on the same network, I can't really make any sense of that. I'd be curious to see the output from the following command on both his computer and the synology: netstat -nr

Here ya go, thanks!

From diskstation, first because it's much shorter:

Kernel IP routing table

Destination Gateway Genmask Flags MSS Window irtt Iface

0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0

172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0

192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1




From computer: "netstat -nr" output:


Routing tables


Internet:

Destination Gateway Flags Refs Use Netif Expire

default 192.168.2.1 UGSc 93 0 en0

127 127.0.0.1 UCS 0 0 lo0

127.0.0.1 127.0.0.1 UH 6 24676 lo0

169.254 link#8 UCS 1 0 en0 !

192.168.2 link#8 UCS 12 0 en0 !

192.168.2.1/32 link#8 UCS 1 0 en0 !

192.168.2.1 18:31:bf:aa:75:20 UHLWIir 32 32 en0 1192

192.168.2.16 e4:e4:ab:f0:cc:4 UHLWIi 1 137 en0 173

192.168.2.18/32 link#8 UCS 0 0 en0 !

192.168.2.21 link#8 UHLWIi 2 2 en0 !

192.168.2.43 f0:18:98:2f:8a:e5 UHLWI 0 2 en0 838

192.168.2.47 50:32:37:83:3e:be UHLWIi 1 234 en0 858

192.168.2.52 0:11:d9:39:4c:c5 UHLWI 0 40 en0 1170

192.168.2.60 0:e:58:34:36:ae UHLWI 0 0 en0 1189

192.168.2.137 dc:2b:2a:97:58:75 UHLWI 0 0 en0 635

192.168.2.154 0:e0:4c:68:5:3d UHLWI 0 1 en0 1199

192.168.2.158 80:b0:3d:ef:f2:8d UHLWIi 1 213 en0 670

192.168.2.185 0:11:32:18:ed:ff UHLWIi 1 2075463 en0 711

192.168.2.186 9c:e6:5e:9:1e:48 UHLWI 0 70 en0 294

192.168.2.255 ff:ff:ff:ff:ff:ff UHLWbI 0 9 en0 !

224.0.0/4 link#8 UmCS 2 0 en0 !

224.0.0.251 1:0:5e:0:0:fb UHmLWI 0 0 en0

239.255.255.250 1:0:5e:7f:ff:fa UHmLWI 0 404 en0

255.255.255.255/32 link#8 UCS 1 0 en0 !

255.255.255.255 ff:ff:ff:ff:ff:ff UHLWbI 0 6 en0 !

 

[NuShrike]

Is your router set to block traffic WiFi from seeing wired traffic? It's an optional security setting, or part of guest WiFi.

Or you've set up a vlan somewhere?

 

[Story]

Thanks all!

I'm reaching out to Synology support to see what's up ... I can't even ping the router from my Synology command line, so it's clearly not isolated to Docker. Strangely there's very little I can find on the interwebs about this issue.

 

[Story]

OK, the answer is pretty simple -- my account, even though it was in the administrator group, did not have permission to run certain network commands at root privileges. If I "sudo ping 192.168.2.200" then everything worked fine from the terminal. Who knew that "ping" would be a restricted command!

So...had to log in as Admin, and run the docker image as Admin. It's running now and I'll see if it produces good data.

I'll probably end up running two, one for solar generation and one for consumption, but for now I just want to see solar production.

 

[dotbombjoe]

Great, glad you were able to figure it out. It is nice to have both generation and consumption data available.

 

[Story]

Great, glad you were able to figure it out. It is nice to have both generation and consumption data available.

Yeah, makes sense...do you just run two docker images, identically configured except for the "output" parameter?

 

[dotbombjoe]

Yeah, makes sense...do you just run two docker images, identically configured except for the "output" parameter?

It has been a while since I looked at the setup and I still haven't converted over to the docker images but I think that's the basic idea, yes. I'm just not sure if other aspects of the config change or not. I'm on vacation so I can't check my config right now but perhaps someone else has a better answer in the meantime.