502 POST https://fra-storage.proton.me/storage/blocks: 502 Bad Gateway (Code=0, Status=502)" error

[spyspirit0]

System Health details

System Information

version	core-2025.12.4
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
container_arch	amd64
user	root
virtualenv	false
python_version	3.13.9
os_name	Linux
os_version	6.12.51-haos
arch	x86_64
timezone	America/Toronto
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	5000
Installed Version	2.0.5
Stage	running
Available Repositories	2565
Downloaded Repositories	63

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 16.3
update_channel	stable
supervisor_version	supervisor-2025.12.3
agent_version	1.7.2
docker_version	28.3.3
disk_total	468.7 GB
disk_used	34.8 GB
nameservers	9.9.9.9, 8.8.8.8, 1.1.1.1, 76.76.2.0
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	generic-x86-64
supervisor_api	ok
version_api	ok
installed_addons	Bookstack (4.0.2), TasmoBackup (1.06.09), Terminal & SSH (9.21.0), Zigbee2MQTT (2.7.1-1), Simple Scheduler (3.2.2), Mosquitto broker (6.5.2), Matter Server (8.1.2), MariaDB (2.7.2), ESPHome Device Builder (2025.12.2), TasmoAdmin (0.33.0), Tailscale (0.26.1), phpMyAdmin (0.13.0), Log Viewer (0.17.1), Firefox (1.9.0), File editor (5.8.0), OpenThread Border Router (2.15.3), Home Assistant Time Machine (2.1.0), SONOFF Dongle Flasher (1.2.3)

Dashboards

dashboards	3
resources	38
views	17
mode	storage

Network Configuration

adapters	lo (disabled), enp1s0 (enabled, default, auto), hassio (disabled), docker0 (disabled), vethc1536ed (disabled), veth45d9bc3 (disabled), vethb3ac9cc (disabled), veth7d92771 (disabled), veth5f011ee (disabled), vethc61d32b (disabled), veth6c021e8 (disabled), vethe11c772 (disabled), veth7852ded (disabled), veth64f0203 (disabled), veth7eb6233 (disabled), veth59bd22a (disabled), vethbe2a8c2 (disabled), vetheb4f361 (disabled), veth3d86bab (disabled), veth32e308a (disabled), vetha183ad4 (disabled), veth18110d0 (disabled)
ipv4_addresses [REDACTED]
ipv6_addresses [REDACTED]

Recorder

oldest_recorder_run	16 décembre 2025 à 11:21
current_recorder_run	28 décembre 2025 à 07:00
database_engine	mysql
database_version	10.11.6

Checklist

• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This issue is not a duplicate issue of any previous issues..

Describe the issue

I installed the integration on 2025-12-26, logged into my proton account with 2fa and was able to do a manual backup then, it worked, I see the backup in my Proton Drive.

Now (2025-12-28), when there is an automatic backup running or I trigger a manual or automatic backup, it saves to all my other locations but it's failing to save to Proton Drive.

Getting an "API Error: failed to upload backup", "502 POST https://fra-storage.proton.me/storage/blocks: 502 Bad Gateway (Code=0, Status=502)" error.

I tried removing the integration, re-downloading it, re-adding it in HA, sign in again, reset the backup location in HA, trigger a backup.

Reproduction steps

1. Add Proton Drive integration from HACS
2. Add Proton Drive integration in HA
3. Sign into Proton account with 2fa
4. Start an automatic or manual backup

It fails on Proton but works on other locations (Local, NAS, Google Drive).

Debug logs

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun home-assistant (no readiness notification)
s6-rc: info: service legacy-services successfully started
2025-12-28 14:39:49.378 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration battery_notes which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.379 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration proton_drive which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.379 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.380 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ha_visualiser which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.380 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook_inverse which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.381 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration moonraker which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.381 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration midea which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.381 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration kwikset which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.382 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration wigle which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.382 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ble_monitor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.382 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration pfsense which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.382 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration adaptive_lighting which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.383 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration llmvision which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.383 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration smartthinq_sensors which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.383 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration presence_simulation which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.384 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration vesync_formatbce which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.384 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alarmo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.384 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration watchman which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.384 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration mjpeg_timelapse which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.385 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration scheduler which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.385 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tplink_router which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.385 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration activity_manager which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.385 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration truenas which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.386 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.386 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration fontawesome which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.386 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration battery_notes which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.387 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration proton_drive which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.387 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.387 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ha_visualiser which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.387 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration spook_inverse which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.388 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration moonraker which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.388 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration midea which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.388 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration kwikset which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.389 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration wigle which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.389 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration ble_monitor which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.389 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration pfsense which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.389 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration adaptive_lighting which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.390 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration llmvision which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.390 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration smartthinq_sensors which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.390 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration presence_simulation which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.390 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration vesync_formatbce which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.391 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alarmo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.391 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration watchman which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.391 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration mjpeg_timelapse which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.391 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration scheduler which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.392 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tplink_router which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.392 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration activity_manager which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.392 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration truenas which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.393 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:49.393 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration fontawesome which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2025-12-28 14:39:51.171 WARNING (MainThread) [homeassistant.helpers.config_validation] The 'include' option near /config/configuration.yaml:59 is deprecated, please remove it from your configuration
2025-12-28 14:39:51.172 WARNING (MainThread) [homeassistant.helpers.config_validation] The 'use_include_order' option near /config/configuration.yaml:59 is deprecated, please remove it from your configuration
2025-12-28 14:39:52.635 ERROR (SyncWorker_4) [homeassistant.components.plex.server] Not authorized to access plex.tv with provided token
2025-12-28 14:39:52.635 WARNING (SyncWorker_4) [homeassistant.components.plex.server] Plex account has limited permissions, shared account filtering will not be available
2025-12-28 14:39:57.790 ERROR (SyncWorker_4) [custom_components.truenas.api] TrueNAS [REDACTED] query (update.check_available) error: Method does not exist
2025-12-28 14:39:59.582 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.739 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.740 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.740 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.741 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.741 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.742 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.743 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.743 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.745 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.746 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.747 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.747 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.749 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.750 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.750 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.751 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.752 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.753 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.753 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.754 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.758 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.759 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.760 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.761 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.762 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.763 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.764 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.765 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.766 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.767 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:39:59.769 WARNING (MainThread) [env_canada.ec_map] Map from https://maps.geogratis.gc.ca/wms/CBMT could not be retrieved: Cannot connect to host maps.geogratis.gc.ca:443 ssl:default [DNS server returned answer with no data]
2025-12-28 14:40:02.976 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for chicken-coop-esp32 @ [REDACTED]: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='[REDACTED]', port=6053))]: [Errno 113] Connect call failed ('[REDACTED]', 6053) (SocketAPIError)
2025-12-28 14:40:02.977 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for vindriktning-air-quality-1 @ [REDACTED]: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='[REDACTED]', port=6053))]: [Errno 113] Connect call failed ('[REDACTED]', 6053) (SocketAPIError)
2025-12-28 14:40:02.979 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for ender3-s1-light @ [REDACTED]: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='[REDACTED]', port=6053))]: [Errno 113] Connect call failed ('[REDACTED]', 6053) (SocketAPIError)
2025-12-28 14:40:05.248 WARNING (SyncWorker_3) [urllib3.connectionpool] Retrying (Retry(total=0, connect=1, read=1, redirect=None, status=None)) after connection broken by 'SSLError(SSLEOFError(8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1032)'))': /
2025-12-28 14:40:13.253 WARNING (SyncWorker_3) [qbittorrentapi.request] Using 'http' instead of requested 'https'to communicate with qBittorrent
2025-12-28 14:40:18.545 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.wyze_salon] Error from stream worker: Timestamp discontinuity detected: last dts = 215998, dts = 4211539687
2025-12-28 14:41:01.386 ERROR (MainThread) [homeassistant.components.iss] Error fetching iss data: Unable to retrieve data
2025-12-28 14:42:51.754 WARNING (MainThread) [homeassistant.components.zha.backup] No ZHA gateway exists, skipping coordinator backup
2025-12-28 14:46:17.389 ERROR (MainThread) [homeassistant.components.iss] Error fetching iss data: Unable to retrieve data
2025/12/28 14:46:56.918593 WARN RESTY 502 POST https://zrh-storage.proton.me/storage/blocks: 502 Bad Gateway (Code=0, Status=502), Attempt 1
2025/12/28 14:46:56.918647 ERROR RESTY 502 POST https://zrh-storage.proton.me/storage/blocks: 502 Bad Gateway (Code=0, Status=502)
2025-12-28 14:46:56.927 ERROR (MainThread) [custom_components.proton_drive] proton API call failed
Traceback (most recent call last):
  File "/config/custom_components/proton_drive/api.py", line 208, in __call_api
    return await hass.async_add_executor_job(call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/proton_drive/api.py", line 180, in <lambda>
    call=lambda: folder.Upload(
                 ~~~~~~~~~~~~~^
        self._instance_id,
        ^^^^^^^^^^^^^^^^^^
    ...<3 lines>...
        str(f.name),
        ^^^^^^^^^^^^
    ),
    ^
  File "/usr/local/lib/python3.13/site-packages/proton/proton.py", line 160, in Upload
    self._client._exec(
    ~~~~~~~~~~~~~~~~~~^
        "upload",
        ^^^^^^^^^
    ...<5 lines>...
        content_path=contentPath,
        ^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/proton/proton.py", line 226, in _exec
    return _call_go_exec(
        "with-creds",
    ...<4 lines>...
        **kwargs,
    )
  File "/usr/local/lib/python3.13/site-packages/proton/proton.py", line 101, in _call_go_exec
    raise RuntimeError(error)
RuntimeError: failed to upload backup "Automatic_backup_2025.12.4_2025-12-28_14.42_51743361.tar": 502 POST https://zrh-storage.proton.me/storage/blocks: 502 Bad Gateway (Code=0, Status=502)
2025-12-28 14:46:57.149 ERROR (MainThread) [homeassistant.components.backup] Upload failed for [REDACTED]: Failed to upload backup: API Error: failed to upload backup "Automatic_backup_2025.12.4_2025-12-28_14.42_51743361.tar": 502 POST https://zrh-storage.proton.me/storage/blocks: 502 Bad Gateway (Code=0, Status=502)
2025-12-28 14:47:36.860 ERROR (MainThread) [frontend.js.modern.202512033] Uncaught error from Chrome WebView 143.0.7499.115 on Android 16
Error: Failed to execute 'define' on 'CustomElementRegistry': the name "remote-button" has already been used with this registry
A.define (node_modules/@webcomponents/scoped-custom-element-registry/src/scoped-custom-element-registry.ts:180:12)
a.define (/hacsfiles/tabbed-card/tabbed-card.js:63:109)
/hacsfiles/universal-remote-card/universal-remote-card.min.js:17:6596
_ (/hacsfiles/universal-remote-card/universal-remote-card.min.js:35:4761)
/hacsfiles/universal-remote-card/universal-remote-card.min.js:35:9148
/hacsfiles/universal-remote-card/universal-remote-card.min.js:81:3944
/hacsfiles/universal-remote-card/universal-remote-card.min.js:81:3948
2025-12-28 14:47:36.886 ERROR (MainThread) [frontend.js.modern.202512033] Uncaught error from Chrome WebView 143.0.7499.115 on Android 16
Error: Failed to execute 'define' on 'CustomElementRegistry': the name "focus-trap" has already been used with this registry
A.define (node_modules/@webcomponents/scoped-custom-element-registry/src/scoped-custom-element-registry.ts:180:12)
a.define (/hacsfiles/tabbed-card/tabbed-card.js:63:109)
/hacsfiles/advanced-camera-card/card-b98d578d.js:70:3686

Diagnostics dump

I don't see a way to download diagnostic logs for this integration.

[LouisBrunner]

Hi @lefebp, thank you for your report.

Getting an "API Error: failed to upload backup", "502 POST https://fra-storage.proton.me/storage/blocks: 502 Bad Gateway (Code=0, Status=502)" error.

I have been getting some authentication issues these days (no way to reproduce yet) but not a 502. I will see if I can reproduce it but I doubt it.
Only thing I can think of is that it could be linked to your geographic location but I am not sure what restrictions Proton has there.

I tried removing the integration, re-downloading it, re-adding it in HA, sign in again, reset the backup location in HA, trigger a backup.

I take from your message that this doesn't fix the issue? When I get authentication errors, just "reload"ing the integration is usually enough to fix it.

[spyspirit0]

I have been getting some authentication issues these days (no way to reproduce yet) but not a 502. I will see if I can reproduce it but I doubt it.
Only thing I can think of is that it could be linked to your geographic location but I am not sure what restrictions Proton has there.

I am in Canada if that matters, I'll try to do some research about this.

I take from your message that this doesn't fix the issue? When I get authentication errors, just "reload"ing the integration is usually enough to fix it.

Correct, it does not fix the issue, it appear to be signing in correctly when setuping the integration but fails when a backup is initiated.

[EricBmm]

Hi,
just let you know, i got the same error (502 Bad Gateway) Last sucessful Backup was 25.12. after that it seem to be broken. A manual Backup didnt work either. Because it was mentioned before, my location is Germany.

Erstmals aufgetreten: 1. Januar 2026 um 23:04:23 (7 Vorkommnisse)
Zuletzt protokolliert: 17:43:33
proton API call failed
Traceback (most recent call last):
File "/config/custom_components/proton_drive/api.py", line 208, in __call_api
return await hass.async_add_executor_job(call)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/proton_drive/api.py", line 180, in
call=lambda: folder.Upload(
~~~~~~~~~~~~~^
self._instance_id,
^^^^^^^^^^^^^^^^^^
...<3 lines>...
str(f.name),
^^^^^^^^^^^^
),
^
File "/usr/local/lib/python3.13/site-packages/proton/proton.py", line 160, in Upload
self._client._exec(
~~~~~~~~~~~~~~~~~~^
"upload",
^^^^^^^^^
...<5 lines>...
content_path=contentPath,
^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/site-packages/proton/proton.py", line 226, in _exec
return _call_go_exec(
"with-creds",
...<4 lines>...
**kwargs,
)
File "/usr/local/lib/python3.13/site-packages/proton/proton.py", line 101, in _call_go_exec
raise RuntimeError(error)
RuntimeError: failed to upload backup "Automatic_backup_2025.12.5_2026-01-01_23.00_00001315.tar": 502 POST https://fra-storage.proton.me/storage/blocks: 502 Bad Gateway (Code=0, Status=502)

[spyspirit0]

Some interresting observations, it appear to be somewhat intermittent.

Over the week-end, I had two of my nightly automatic backups that successfully saved the backups in Proton Drive (Jan. 03 and Jan. 04 both at around 05h30 EST), I see the files in Proton Drive and HA shows the backups as successful and saved in Proton Drive. I tried another two manual backups yesterday, Jan. 04, later at night at around 22h05 using the Create backup button and selecting Automatic Backup and they failed.

I'm at work and don't really have the time to look into the logs but will update if I find something relevant once I get home or find some time during lunch.

Must be some kind of changes, throttling or restriction on Proton's side.

[EricBmm]

Can confirm this behavior.
Successful upload to Proton Drive 04.01. at 11:00 PM. Manual Update doesnt work now, same error as before.

[LouisBrunner]

@EricBmm Thank you for confirming.

Do either of you use a VPN? What's the rough size of your backup?

Potentially it could be related to this: garethgeorge/backrest#1002

I just setup a fresh dev HA instance and still couldn't reproduce. If it is similar to the above issue and just a matter of retrying then that wouldn't be too hard but without being able to test it directly, it's going to be challenging to implement.

I am going to look into adding more debug so we can know a bit more what is going on and I'll get back to you.

[spyspirit0]

Thanks. Yeah it's not ideal if it can''t be reproduced.

I dont't use a VPN on my HA server at all (baremetal), I only use VPN on another file server for a very specific set of containers only (completely seperate machine on another IP).

My average backup size if about 3.04GB.

Edit: sorry, ralizied that it was addressed to @EricBmm 🙃

[MiMillieuh]

From my experience, it's file size related. when I have files that are more than 2-3 GB it fails with a 502 error on Rclone or anything I try to use to upload to protondrive.

[spyspirit0]

From my experience, it's file size related. when I have files that are more than 2-3 GB it fails with a 502 error on Rclone or anything I try to use to upload to protondrive.

Interresting, I'll try to bakcup HA only without anything else, should be less than 1GB.

[spyspirit0]

From my experience, it's file size related. when I have files that are more than 2-3 GB it fails with a 502 error on Rclone or anything I try to use to upload to protondrive.

Interresting, I'll try to bakcup HA only without anything else, should be less than 1GB.

Well, 342MB, it worked... i think you got something here.

[LouisBrunner]

Edit: sorry, ralizied that it was addressed to @EricBmm 🙃

All good, I was asking you as well. 😄

From my experience, it's file size related. when I have files that are more than 2-3 GB it fails with a 502 error on Rclone or anything I try to use to upload to protondrive.

Thanks for jumping in! Do you know the sweet spot where uploads usually don't fail? Does retrying make any difference?

Can't believe I forgot to check the error code of #47, because it's the same. 🤦

I might look into a way to split the backup into chunks, it will be a bit more brittle but at least it will work for bigger uploads.

[EricBmm]

No VPN for me either but you got here a hot trace anyway.. :-)
My sucessful Backups (3) has :2.2, 2.2 and the last 2.5 GB.... and just in this second i can confirm, a manual test backup without addons and only 689 MB was sucessful uploaded to Proton Drive.

EDIT: As @MiMillieuh told us before its known for Rclone too. I found this thread at the RcLone Community

[GuiPoM]

Hello!

I also have some issues with my proton backups, no VPN, very good fiber connection, relatively small backups (400 mb). But it regularly fails.

Cette erreur provient d'une intégration personnalisée

Enregistreur: custom_components.proton_drive
Source: custom_components/proton_drive/api.py:208
intégration: Proton Drive (documentation, problèmes)
S'est produit pour la première fois: 04:59:05 (1 occurrence)
Dernier enregistrement: 04:59:05

proton API call failed
Traceback (most recent call last):
File "/config/custom_components/proton_drive/api.py", line 208, in __call_api
return await hass.async_add_executor_job(call)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/concurrent/futures/thread.py", line 59, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/proton_drive/api.py", line 180, in
call=lambda: folder.Upload(
~~~~~~~~~~~~~^
self._instance_id,
^^^^^^^^^^^^^^^^^^
...<3 lines>...
str(f.name),
^^^^^^^^^^^^
),
^
File "/usr/local/lib/python3.13/site-packages/proton/proton.py", line 160, in Upload
self._client._exec(
~~~~~~~~~~~~~~~~~~^
"upload",
^^^^^^^^^
...<5 lines>...
content_path=contentPath,
^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/usr/local/lib/python3.13/site-packages/proton/proton.py", line 226, in _exec
return _call_go_exec(
"with-creds",
...<4 lines>...
**kwargs,
)
File "/usr/local/lib/python3.13/site-packages/proton/proton.py", line 101, in _call_go_exec
raise RuntimeError(error)
RuntimeError: failed to upload backup "Automatic_backup_2026.1.0_2026-01-08_04.58_29002514.tar": 502 POST https://zrh-storage.proton.me/storage/blocks: 502 Bad Gateway (Code=0, Status=502)

[EricBmm]

So... i changed my Backup settings a little bit, few addons i dont use anymore actual dont get a backup. And the automatic backup tonight was sucessful. Size 2.41 GB. The other sucessful uploads few days ago were 2.48 GB. So it seems the sweet spot ist under 2.5 GB and all above will fail.

[LouisBrunner]

@GuiPoM Weird, mine are around 700MB and I never get this specific failure.

I can start adding chunking for backups above 2GB and see if that tackles the issue reliably.