different behaviour on port 8080?

huey · Post by **huey** » Sunday 22 April 2018 22:09

I must be going mad: when running domoticz on port 8080 it is not possible to switch icon in edit mode of device and the log is showing less. If I start on port 8081, all is ok...

Thanks for any advise on how to resolve this... Not really a problem to run on 8081 but it bugs me that I can not find the reason...

huey · Post by **huey** » Sunday 22 April 2018 22:13

And the log:

huey · Post by **huey** » Sunday 22 April 2018 22:16

While ok:

waaren · Post by **waaren** » Sunday 22 April 2018 22:24

If I look very closely at you screen shots I can see that you use V3.9288 but I cannot see what your hardware or OS you are using for your domoticz instance.
That information might be useful in getting to an answer

huey · Post by **huey** » Sunday 22 April 2018 22:30

Hi waaren,

Yes, you are right: I use the beta builds on a Raspberry PI 2, Debian Stretch, added python 3.6.5 and build from source with USE_OPENSSL_STATIC=NO so I can make use of ptyhon plugins without segmentation faults. Although
I think the last items are not relevant for this matter. I have this behaviour also on earlier beta builds.

huey · Post by **huey** » Sunday 22 April 2018 23:31

Hm, just noticed that giving the host a different name also solves the issue. I guess the webserver does not like the host to be domoticz as it maybe uses it internally as well fro some check on port 8080?
Renamed the host to domoticz-prod.local and know am running on port 8080 with the proper edit and log functionality...

Still interested to know what is really going on. Would be great if someone was able to explain/elaborate?

gizmocuz · Post by **gizmocuz** » Monday 23 April 2018 6:27

Try clearing your browser cache and appcache (two different things)

huey · Post by **huey** » Monday 23 April 2018 7:58

gizmocuz wrote:Try clearing your browser cache and appcache (two different things)

Ok, I will give that a try!

huey · Post by **huey** » Monday 23 April 2018 21:30

Ok, my bad: clearing the appcache did it! Must admit I was not aware/stumbled upon the existance, of that cache. Must browse more topics.

@gizmocuz: Thanks for solving this issue for me!

different behaviour on port 8080?

different behaviour on port 8080?

Re: different behaviour on port 8080?

Re: different behaviour on port 8080?

Re: different behaviour on port 8080?

Re: different behaviour on port 8080?

Re: different behaviour on port 8080?

Re: different behaviour on port 8080?

Re: different behaviour on port 8080?

Re: different behaviour on port 8080?

Who is online