Home Automation Domotica Forum Europe, Bwired Forum

After a new instalation, i can't start the webserver in the source anymore
and i need that for the plugwise plugin

Gr Ruud

Maybe the webserver port is already in use?
Try changing it as test, and see if it will start.

--

If i browse directly to the plugwise server to port 8080 local host its responding well.

So what's not working then?

Rene.

Which OS are you running on? In Vista I need to start the source program as administrator.

os xp prof and i can't start de webserver in de source.

gr Ruud

Ok, so try right-click on the source icon and choose Run as administrator. Then try to start the webserver. I guess it has something to do with the security policy in windows.

But if 8080 local is responding well, the webserver is running fine.

--

After a reinstall as admin , same results. Grr
For the security i have reinstalled the source on my former homeseer pc. You never know what is checked by plugwise. . ( stopped the web-server en reinstall)

Gr Ruud

Removed the whole Plugwise hardware/software shit and replaced the with te good old am12 with KLIK And wait for the plugwise helpdesk "24 hour service" They take you're call en Will callback , but when?????

If you van acces the port local then there must fire wall issue.
Windows Firewall?
Most Anti virus software also block the port 8080

Case closed.
New install with new release source software dus the trick

Gr Ruud

Can I reopen this topic to get help on the same problem?

I have the same symptoms, and did some tests that confused me only more:
- Homeseer webinterface op port 80 is accessible locally and from other PCs (as usual, so far so good).
- Plugwise webinterface on port 8080 is accessible locally but INaccessible from other PCs (the problem described in this topic).

I did the following to test if a firewall is involved:
- Changing Plugwise to port 81 does not make it accessible from other PCs (it is accessible locally on port 81).
- Stopping homeseer and changing Plugwise portnumber to 80 does not make it accessible from other PCs (it is accessible locally on port 80).
- then starting Homeseer results in Homeseer automatically changing to port 81 (nice feature:-), which is accessible from other PCs. This confirms port 80 is indeed in use (by PlugWise), and port 81 is accessible from other PCs (no firewall blocking it).
- Then stopping Plugwise, changing Homeseer back to port 80, made Homeseer accessible on port 80 again.

- Then starting Plugwise (still set to use port 80) made things go belly up. Neither Homeseer nor Plugwise were accessible on port 80. Changing portnumbers to whatever did not help. In the end the windows(XP) network diagnostics tool had to reset "the catalog of winsock providers" to default, and required a reboot.

This reboot is now going on, but only after installing 28 windows updates, which gives me time to write this post (the laptop in question is a brandnew EEEpc that I installed this weekend).
By the way: I am very happy with the EEEpc as homeserver because it uses only 8,6 Watt when running Homeseer with 2 RFXcom USB modules and Plugwise (screen off)).

Back to the topic:
I don't understand why a single portnumber is accessible from the network when used by Homeseer webserver at one moment, but inaccessible when (after stopping homeseer!-) used by Plugwise webserver at another moment.
Can this somehow be a 'feature' of the Plugwise webserver, or would that be unlikely?
Any suggestions are welcome!

(where I wrote Plugwise I mean the Source program, v20091102.18)

<edited to fix typo's>