Page 1 of 1
NexaHome 1.1.1 with Linux - Web server starting but no page
Posted: Fri Mar 17, 2023 9:45 am
by merbau
Hi,
I have been playing around with Tellstick about a week now. I am using Linux (Fedora 10), and have succesfully configured my system with "tdtool" for using with three NEXA selflearning, and one WAVEMAN receiver.
I have been also using NexaHome program, and it is really nice program!
I have one problem though: When starting NexaHome, it starts web server in my localhost:8080, but browser sees an empty page, when going to
http://localhost:8080/nexahome
There IS a web server running, since stopping NexaHome and going again to
http://localhost:8080/nexahome produces "page not found" error in a browser.
Any clues for debugging?
Thanks.
Posted: Fri Mar 17, 2023 9:45 am
by Jaxån
I am not using NexaHome.
You might want to ask the question here:
http://www.telldus.se/forum/viewtopic.php?t=239
There are more people that knows about NexaHome
Re: NexaHome 1.1.1 with Linux - Web server starting but no p
Posted: Fri Mar 17, 2023 9:45 am
by hekj
merbau wrote:When starting NexaHome, it starts web server in my localhost:8080, but browser sees an empty page, when going to
http://localhost:8080/nexahome
There IS a web server running, since stopping NexaHome and going again to
http://localhost:8080/nexahome produces "page not found" error in a browser.
Any clues for debugging?
Maybe the password is incorrect or not given!
/Henrik
Re: NexaHome 1.1.1 with Linux - Web server starting but no p
Posted: Fri Mar 17, 2023 9:45 am
by merbau
hekj wrote:merbau wrote:When starting NexaHome, it starts web server in my localhost:8080, but browser sees an empty page, when going to
http://localhost:8080/nexahome
There IS a web server running, since stopping NexaHome and going again to
http://localhost:8080/nexahome produces "page not found" error in a browser.
Any clues for debugging?
Maybe the password is incorrect or not given!
/Henrik
I also gave the password, as You mentioned. No luck still.
But I tried NexaHome 1.3.0, and there is a little success: with
http://127.0.0.1:8080/nexahome ,browser sees the hint to give a password:
Code: Select all
&psw=<thepassword> password is incorrect or not given!
So, I see some progress there, but still, when correct password is given, nothing is seen by browser.
Is there anything I can do to help debugging this?
Posted: Fri Mar 17, 2023 9:45 am
by granede
Are you using any national characters in the names of the devices?
I am running NexaHome on linux and had a similar (the same?) problem in the beginning. Webserver started, but no page shown!
But after a hint from user GregB (Thanks!) I reviewed all the device names and replaced all national characters (åäö etc.) i.e. instead of "Fönsterlampa" I used the name "Fonsterlampa".
After that I have a fully working webpage....
Might be worth a try??
Posted: Fri Mar 17, 2023 9:45 am
by merbau
granede wrote:Are you using any national characters in the names of the devices?
I am running NexaHome on linux and had a similar (the same?) problem in the beginning. Webserver started, but no page shown!
But after a hint from user GregB (Thanks!) I reviewed all the device names and replaced all national characters (åäö etc.) i.e. instead of "Fönsterlampa" I used the name "Fonsterlampa".
After that I have a fully working webpage....
Might be worth a try??
Incredible! Thank You for the great tip.
After changing accented character (ö->o), web page now works.
Thanks!
Posted: Fri Mar 17, 2023 9:45 am
by hekj
merbau wrote:granede wrote:Are you using any national characters in the names of the devices?
I am running NexaHome on linux and had a similar (the same?) problem in the beginning. Webserver started, but no page shown!
But after a hint from user GregB (Thanks!) I reviewed all the device names and replaced all national characters (åäö etc.) i.e. instead of "Fönsterlampa" I used the name "Fonsterlampa".
After that I have a fully working webpage....
Might be worth a try??
Incredible! Thank You for the great tip.
After changing accented character (ö->o), web page now works.
Thanks!
I have added "charset=iso-8859-1" to the Content-Type definition on the webpage, please dowload the latest version and try with åäö again.
/Henrik