Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client network socket disconnected before secure TLS connection was established #238

Closed
Goersch opened this issue May 8, 2022 · 10 comments
Labels
bug Something isn't working Fixed Already fixed in current developent branch

Comments

@Goersch
Copy link

Goersch commented May 8, 2022

iobroker always disables adapter because of too many restarts. Log of adapter
logs - HA-Server

@Pnuts76
Copy link

Pnuts76 commented May 8, 2022

I also have issues with version 6.1.5 of mielecloudservice adapter and adapter is restarted a lot of time until iobroker completly stops adapter after too many restarts.
The adapter also produces a lot of DNS request for 'api.mcs3.miele.com' so that after a certain time, my pihole begins to reject DNS requests from iobroker for this address.
I attached an excerpt of iobroker logfile regarding the mielecloudservice messages. I hope this helps to find the root cause.
mielecloudservice.log

@Grizzelbee Grizzelbee changed the title 6.1.5 not stable Client network socket disconnected before secure TLS connection was established May 9, 2022
@Grizzelbee Grizzelbee added the bug Something isn't working label May 9, 2022
@Grizzelbee
Copy link
Owner

facing this issue myself too. trying to find a solution.

@Grizzelbee
Copy link
Owner

Grizzelbee commented May 12, 2022

@Pnuts76
Just long term testing V6.2.0 in my productive environment. This version got some improvements and I hope to solve most issues with this release.
Please test this version as soon as it is released in the latest branch and report if it works for you or not.
Especially I am interested in the many DNS requests reported by you since I really expect only a few to occur. DNS requests should only occur:

  • on adapter startup
  • when a device gets powered on
  • On every aktion taken against the API
  • on adapter shutdown

In the meantime the API Server keeps the connection alive and I don't expect any DNS requests during this time.

@Pnuts76
Copy link

Pnuts76 commented May 12, 2022

@Grizzelbee
I will deploy and test the latest version as soon as it is available.
I will also have an eye on DNS requests and give you feedback afterwards.
Thank you for your efforts.

@Grizzelbee
Copy link
Owner

Hmmm. Just read the issue again and took a deeper look into your screenshot...
It may be that the PiHole is causing your issues. I read a few times something about "wrong proxy setup in connection request", when googleing the different error messages that we are facing. They were telling to include the proxy in the request options. So it may be that v6.2.0 won't solve your issue (by using SSE) and I need to add a proxy config to the admin page - but this is just thinking loudly. If SSE won't work for you - I reintroduce data polling again.

@Pnuts76
Copy link

Pnuts76 commented May 12, 2022

Did you mean the errors in the logs I attached...? Errors from screenshot are from another user.
I guess, we shoud not have a problem with SSE in combination with pihole, as pihole is just answering the local DNS requests and is not proxying any network traffic in my setup. I suggest to give it a try anyway.

@Pnuts76
Copy link

Pnuts76 commented May 16, 2022

I installed 6.2.0 now and will do some testing during the next days.

@Grizzelbee
Copy link
Owner

Great! On my side 6.2.0 runs pretty stable for three days now. Just logging one error message a day which all solved themself.

@Grizzelbee Grizzelbee added the Fixed Already fixed in current developent branch label May 17, 2022
@Pnuts76
Copy link

Pnuts76 commented May 19, 2022

Just wanted to confirm, that versions >= 6.2 are running fine in my environment. Thank you for your great work!

@Grizzelbee
Copy link
Owner

@Pnuts76

thanks for your confirmation and your warm words.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Fixed Already fixed in current developent branch
Projects
None yet
Development

No branches or pull requests

3 participants