SSL error post update to core-2026.3.0

[dsfsdbvxc]

The problem

Since updating to core-2026.3.0 the Portainer integration seems to have stopped working.

Error in integration GUI shows:

Failed setup, will retry: An error occurred while trying to connect to the Portainer instance: PortainerConnectionError("Unexpected error during GET https://10.112.1.72:9443/api/endpoints: Cannot connect to host 10.112.1.72:9443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1081)')]")

Error message from logs put in "Anything in the logs that might be useful for us?"

Integration settings (no change to set up other that updating HASOS)
Using the URL - https://XXX.XXX.XXX.XXX:9443/
Verify SSL certificate - Enabled

Tried reconfiguring from the GUI using:
Verify SSL certificate - Enabled

Which it accepts, but get the same error. Same with reloading the integration.

Running portainer CE 2.39.0 LTS on a Pi running bookworm

What version of Home Assistant Core has the issue?

core-2026.3.0

What was the last working version of Home Assistant Core?

Yes

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Portainer

Link to integration documentation on our website

https://www.home-assistant.io/integrations/portainer

Diagnostics information

Not available

Example YAML snippet

Anything in the logs that might be useful for us?

Logger: homeassistant.components.portainer.coordinator
Source: helpers/update_coordinator.py:356
integration: Portainer (documentation, issues)
First occurred: 12:04:27 (38 occurrences)
Last logged: 12:26:34

Unexpected error fetching portainer data
Traceback (most recent call last):
  File "/usr/local/lib/python3.14/site-packages/aiohttp/connector.py", line 1313, in _wrap_create_connection
    return await self._loop.create_connection(*args, **kwargs, sock=sock)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/asyncio/base_events.py", line 1198, in create_connection
    transport, protocol = await self._create_connection_transport(
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<2 lines>...
        ssl_shutdown_timeout=ssl_shutdown_timeout)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/asyncio/base_events.py", line 1231, in _create_connection_transport
    await waiter
  File "/usr/local/lib/python3.14/asyncio/sslproto.py", line 581, in _on_handshake_complete
    raise handshake_exc
  File "/usr/local/lib/python3.14/asyncio/sslproto.py", line 563, in _do_handshake
    self._sslobj.do_handshake()
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.14/ssl.py", line 951, in do_handshake
    self._sslobj.do_handshake()
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1081)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.14/site-packages/pyportainer/pyportainer.py", line 152, in _request
    response = await self._session.request(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<5 lines>...
    )
    ^
  File "/usr/local/lib/python3.14/site-packages/aiohttp/client.py", line 779, in _request
    resp = await handler(req)
           ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/aiohttp/client_middlewares.py", line 36, in single_middleware_handler
    return await middleware(req, handler)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 72, in _ssrf_redirect_middleware
    resp = await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/aiohttp/client.py", line 734, in _connect_and_send_request
    conn = await self._connector.connect(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        req, traces=traces, timeout=real_timeout
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.14/site-packages/aiohttp/connector.py", line 672, in connect
    proto = await self._create_connection(req, traces, timeout)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/aiohttp/connector.py", line 1239, in _create_connection
    _, proto = await self._create_direct_connection(req, traces, timeout)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/aiohttp/connector.py", line 1611, in _create_direct_connection
    raise last_exc
  File "/usr/local/lib/python3.14/site-packages/aiohttp/connector.py", line 1580, in _create_direct_connection
    transp, proto = await self._wrap_create_connection(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/usr/local/lib/python3.14/site-packages/aiohttp/connector.py", line 1315, in _wrap_create_connection
    raise ClientConnectorCertificateError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorCertificateError: Cannot connect to host 10.112.1.72:9443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1081)')]

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/portainer/coordinator.py", line 113, in _async_setup
    await self.portainer.get_endpoints()
  File "/usr/local/lib/python3.14/site-packages/pyportainer/pyportainer.py", line 385, in get_endpoints
    endpoints = await self._request("endpoints")
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/pyportainer/pyportainer.py", line 143, in _request
    async for attempt in AsyncRetrying(
    ...<32 lines>...
                raise PortainerConnectionError(msg) from err
  File "/usr/local/lib/python3.14/site-packages/tenacity/asyncio/__init__.py", line 166, in __anext__
    do = await self.iter(retry_state=self._retry_state)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/tenacity/asyncio/__init__.py", line 153, in iter
    result = await action(retry_state)
             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/tenacity/_utils.py", line 99, in inner
    return call(*args, **kwargs)
  File "/usr/local/lib/python3.14/site-packages/tenacity/__init__.py", line 418, in exc_check
    raise retry_exc.reraise()
          ~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.14/site-packages/tenacity/__init__.py", line 185, in reraise
    raise self.last_attempt.result()
          ~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.14/concurrent/futures/_base.py", line 443, in result
    return self.__get_result()
           ~~~~~~~~~~~~~~~~~^^
  File "/usr/local/lib/python3.14/concurrent/futures/_base.py", line 395, in __get_result
    raise self._exception
  File "/usr/local/lib/python3.14/site-packages/pyportainer/pyportainer.py", line 176, in _request
    raise PortainerConnectionError(msg) from err
pyportainer.exceptions.PortainerConnectionError: Unexpected error during GET https://10.112.1.72:9443/api/endpoints: Cannot connect to host 10.112.1.72:9443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1081)')]

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 356, in __wrap_async_setup
    await self._async_setup()
  File "/usr/src/homeassistant/homeassistant/components/portainer/coordinator.py", line 121, in _async_setup
    raise ConfigEntryNotReady(
    ...<3 lines>...
    ) from err
homeassistant.exceptions.ConfigEntryNotReady: An error occurred while trying to connect to the Portainer instance: PortainerConnectionError("Unexpected error during GET https://10.112.1.72:9443/api/endpoints: Cannot connect to host 10.112.1.72:9443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate (_ssl.c:1081)')]")

Additional information

No response

[home-assistant]

Hey there @erwindouna, mind taking a look at this issue as it has been labeled with an integration (portainer) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of portainer can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign portainer Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@dsfsdbvxc Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20portainer%22%20
_{^{(message by IssueContext)}}

---

portainer documentation
portainer source
_{^{(message by IssueLinks)}}

[ioannispelelis]

had something similar after update
It would not let met uncheck the verify ssl option (since i am using selfsigned certificate on portainer)..
Portainer integration thought i had not done any changes.. apparently unchecking SSL does not count as a change :( and does not save changes.
I tried to fool it no luck
The only thing that worked for me is to regenerate a new token in portainer. enter the new token and uncheck verify SSL at the same time
That way it understood that something had changed (since token was different) and let me save witth verify SSL off and it connected again..
Only downside it recreated all my sensors with a "_2" at the end so now i am deleting old sensors and renaming new sensors without the "_2" at the end so my dashboards and automations are not messed up

[igalg99]

I dont know how it related exactly but also for me after the update the integration is not working but only with the portainer on my synology Nas. I have another one on another machine where integration still works and connects. but more strange than that , by attempting and retrying to connent its spiked up my nas CPU usage to 370% making everyting sluggish. I was troubleshooting for hours to understand where it comes from and the only thing that reulted in reliving the CPU was to disable the portainer integration. the HA is running on a dedicated seperated device. I have confirmed it related by trying to enable the integration again and then again my CPU on the NAS went through the roof. disabling the integration again resolved it so it is directly related just not sure how.

[steffenrapp]

I'm getting timeout errors since the update and similar symptoms like @igalg99
HA is running on a HA Yellow and Portainer on a NAS. After deactivating the Portainer integration the CPU usage of the NAS went back down to normal.

[dsfsdbvxc]

had something similar after update It would not let met uncheck the verify ssl option (since i am using selfsigned certificate on portainer).. Portainer integration thought i had not done any changes.. apparently unchecking SSL does not count as a change :( and does not save changes. I tried to fool it no luck The only thing that worked for me is to regenerate a new token in portainer. enter the new token and uncheck verify SSL at the same time That way it understood that something had changed (since token was different) and let me save witth verify SSL off and it connected again.. Only downside it recreated all my sensors with a "_2" at the end so now i am deleting old sensors and renaming new sensors without the "_2" at the end so my dashboards and automations are not messed up

Thank you, that's useful to know.

That worked for me too. I ended up removing the two Portainer services I had set up, spotted some naming errors needing correcting any way. Re-adding with SSL unticked (not using SSL) and fresh API keys worked, although not sure if the latter was needed.

[ioannispelelis]

Thank you, that's useful to know.

I ended up removing the two Portainer services I had set up as spotted some naming errors needing correcting any way. Re-adding with SSL unticked (not using SSL) and fresh API keys worked, although not sure if the latter was needed.

If you removed it completely and recreated i guess recreating the API was maybe not useful.
In my case i wanted to avoid deleting and recreating to avoid loosing my sensors.
So i was trying to fool the integration by making it think i made a modification
--> since just unchecking verify ssl was not considered as a change in settings (which for me is a bug)

-->changing the IP or Port would not work since putting something random there would cause the integration to check the ip/port and see there is nothing responding on that random ip and port and refuse saving..
--> changing the api key with some random key would do the same since the api key would not be valid, the check would fail connection and would refuse saving

So to "fool it I generated a new API key entered it in the integration to replace old key at the same time i unchecked the verify ssl and it accepted that way both changes..
But in the end it recreated all entities in double so i had to do some tinkering to rename entities so i dont loose history and graphs.

[erwindouna]

Try to reconfigure the entry an uncheck the SSL verify if checked.

[steffenrapp]

Try to reconfigure the entry an uncheck the SSL verify if checked.

I already did that but it didn't solve my issue with the timeout and CPU performance.

[jwhobbie]

I observe same problem with my HA 2026.3.0 revision running as a docker container.

Error message:
Einrichtungsfehler, wird erneut versucht: Timeout error while accessing GET https://hostname:9443/api/endpoints/3/docker/system/df:_

Deleting and reinstalling the Portainer-installation has fixed the problem only temporary.

[erwindouna]

I observe same problem with my HA 2026.3.0 revision running as a docker container.

Error message: Einrichtungsfehler, wird erneut versucht: Timeout error while accessing GET hostname:9443/api/endpoints/3/docker/system/df:_

Deleting and reinstalling the Portainer-installation has fixed the problem only temporary.

Just checking, is endpoint 3 offline and therefore not able to check the df?

[dannykreynin]

I think the verify ssl function is keep defaulting to enabled, making the integration to fail the ssl nego and timeout.

changed the ssl function to False did the trick,
/components/portainer/init.py
client = Portainer( api_url=entry.data[CONF_URL], api_key=entry.data[CONF_API_TOKEN], session=async_create_clientsession( ****=****, verify_ssl=False
from ****= ****, verify_ssl=entry.data[CONF_VERIFY_SSL]
ha core restart

and

the integration is working again!

[Caligo82]

This works, many thanks.

In my case the whole path inside the shell was

/usr/src/homeassistant/homeassistant/components/portainer/

and the file was

__init__.py

the line to edit was number 51 in my init.py

[BNMBOB]

Seeing the same issue (since update to 2026.3.0), "Verify SSL certificate" is now enabled and cannot be disabled. when disabling, HA says "Device is already configured". Looked for the components folder to change the SSL (Hack) but no luck. Can we get a fix so the "Verify SSL certificate" flag can be disabled?

[erwindouna]

Can someone of maybe remember the previous version you had? For instance, did you upgrade a rather big leap from version 2025.10 to 2026.3?