Can't upload firmware since v1.13.1

ppmt · May 31, 2019, 8:56pm

Today I noticed that the plugin has been updated from 1.12.2 to 1.13.1 and assume that I had to upload the new firmware…

Somehow it doesn’t work. Whenever I press upload, showlog or validate I see the screen displaying Terminated Process

In the plugin’s log I see the following errors

INFO 200 POST /edit?configuration=esp_webcam.yaml (0.0.0.0) 5.56ms
WARNING 403 GET /upload (0.0.0.0) 1.73ms
WARNING 403 GET /ace (0.0.0.0) 1.76ms
WARNING 403 GET /ace (0.0.0.0) 1.97ms
WARNING 403 GET /ace (0.0.0.0) 2.36ms
WARNING 403 GET /ace (0.0.0.0) 1.82ms
WARNING 403 GET /ace (0.0.0.0) 1.78ms
WARNING 403 GET /ace (0.0.0.0) 1.81ms
WARNING 403 GET /ace (0.0.0.0) 1.91ms
WARNING 403 GET /ace (0.0.0.0) 2.72ms

I have restarted the plugin, and also hassio and homeassistant but nothing fixes it

CBRHerms · May 31, 2019, 9:59pm

Same here.

HassOS 2.11
Homeassistant 0.93.2
esphome 1.13.1
Proxmox VM

I get nothing in the plugin log, but I do get errors in the hassio log as follows:

19-05-31 21:48:31 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status'
19-05-31 21:48:35 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status'
19-05-31 21:48:37 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status'
19-05-31 21:48:41 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status'
19-05-31 21:48:43 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status'
19-05-31 21:48:47 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status'
19-05-31 21:48:49 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status'
19-05-31 21:48:52 ERROR (MainThread) [aiohttp.server] Unhandled exception
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 448, in start
    await resp.write_eof()
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_response.py", line 444, in write_eof
    await self._payload_writer.write_eof(data)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/http_writer.py", line 138, in write_eof
    self._write(chunk)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/http_writer.py", line 67, in _write
    raise ConnectionResetError('Cannot write to closing transport')
ConnectionResetError: Cannot write to closing transport
19-05-31 21:48:52 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status'
19-05-31 21:48:55 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status'
19-05-31 21:48:57 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status'
19-05-31 21:48:59 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status'
19-05-31 21:49:01 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status'
19-05-31 21:49:02 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status'
19-05-31 21:49:07 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status'
19-05-31 21:49:07 ERROR (MainThread) [hassio.api.ingress] Ingress error: 403, message='Invalid response status'

CBRHerms · May 31, 2019, 10:06pm

So dug a little more, and it appears that when opened via ingress i’m getting the 403 in the logs and terminated process (also getting the same error in the esphome log as you were now).

re added the 6052 port under the network heading which allowed me to connect over http://serverip:6052 and was then able to validate, compile, upload etc.

6052

Looks like a bug with the process running through ingress but that should get you up and running for the time being.

aidbish · May 31, 2019, 10:55pm

Suggest posting issue in the ESPhome github page

nickrout · May 31, 2019, 11:11pm

By the way 1.13.2 is now released.

ppmt · June 1, 2019, 7:45am

@CBRHerms. Yes that fixed the problem.

Thanks a lot for that. I am now at 1.13.2 as well

Just need to flag it up. I will write a bug report on the github page.

renat · June 4, 2019, 5:42am

I have this error to. Can you solve this error?

nickrout · June 4, 2019, 5:50am

Good Lord, read the thread.

renat · June 4, 2019, 6:01am

Add in your post that fix work only with disabled ssl in esphome config.
Thanks

nickrout · June 4, 2019, 6:40am

You said you had the same problem. That problem is solved in third post on the thread. Now you say (I think, your post actually makes not grammatical sense) that there is an ssl problem. That is a different problem.

Also there is an issue posted, did you read it?

bpmittal · June 15, 2019, 7:02pm

i am also having this same issue after esphome ingress .
any permanent solution ?

nickrout · June 15, 2019, 7:43pm

Read the thread

renat · June 17, 2019, 5:26am

“Ssl”: false, in esphome config.
Enter 6052 port number in “Network Configuration”. Labeled as “host”.
Restart esphome
Now you can access to esphome with local ip address. Example link: http://192.168.10.10:6052

bpmittal · September 18, 2019, 6:24pm

i am also having this problem while using ingress , but it is working fine when i use through port 6052 .

and solution of this ingress problem ?

MNL · October 19, 2023, 2:05pm

This worked for me with HA 2023.10.0 and ESPHome. Thanks. Now I was being able to update my devices. Within HA all I got was a black screen where normally the update of my devices is running.