[BUG] Gateway Error in version 1.7.0

[thundergreen]

Describe the bug
A clear and concise description of what the bug is.
Last Frigate Beta Release 1.7.0 gives Bad Gateway Error

Version of Double Take
Current version: 1.7.0

Expected behavior
A clear and concise description of what you expected to happen.
Working Webinterface

Screenshots
If applicable, add screenshots to help explain your problem.

Hardware

• OS: [e.g. Ubuntu, macOS, Windows]
• Browser (if applicable) [e.g. Chrome, Safari]
  HassOS Intel NUC / Chrome Browser

Additional context
Add any other context about the problem here.

Version 1.6.0 Works perfectly
my Addon Config:

Log doube-take:

info: Double Take v1.7.0-456a6ff

Log Supervisor
21-11-30 00:03:17 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.14:3000 ssl:default [Connect call failed ('172.30.33.14', 3000)]

[thundergreen]

No news here? How can i roll back to 1.6.x if no backup available? :(

[thundergreen]

Any news ?

[jakowenko]

I'm not able to reproduce this and haven't heard of anyone else having this issue at the moment. Can you post your current config file? I'm a bit baffled why this would randomly pop up.

Does the UI show up if you go to the port directly and bypass Ingress?

[thundergreen]

hello, I had zwave addon also running on that port. Now I removed zwave addon to expoe port 3000 but still the same error persists. I have absolutely no idea why it does work with version 1.6.0 and not with 1.7.x What can i do to help you with that? Bypassing ingress does the ssame. BAD gateway. I have nothing in the logs of your addon but:

info: MQTT: connected
info: MQTT: subscribed to frigate/events, frigate/+/person/snapshot```

[lroubinov]

having the same problem
502: bad gateway
help :)?

[thundergreen]

There is an issue with the latest hassio addon.

here is a fork:
https://github.com/rubenoost/double-take-hassio-addons

remove ORIGINAL from repo addon and replace with this one and install STABLE addon. You will see it will work again :)

SECRET_PATH somehow makes problems

[smoke007]

I got this error recently and found this thread. I found that after I restarted my Frigate server, the error was gone and Double Take started working again. - Update, the problem came back and it's staying broke...

It looks like the reason mine has started working again usually is because I'd enabled Watchdog for the Double Take addon, so it would restart it over and oven until it would eventually load, but now it no longer will.

Here are the logs:

22-03-04 12:19:52 info: Double Take v1.7.0-bf3e911
22-03-04 12:19:52 verbose: {
auth: false,
detect: {
match: {
save: true,
base64: false,
confidence: 60,
purge: 340,
min_area: 2500
},
unknown: {
save: true,
base64: false,
confidence: 0,
purge: 340,
min_area: 0
}
},
time: { timezone: 'UTC' },
frigate: {
attempts: { latest: 10, snapshot: 10, mqtt: true, delay: 0 },
image: { height: 500 },
labels: [ 'person' ],
url: 'http://192.168.86.100:5001'
},
mqtt: {
topics: {
frigate: 'frigate/events',
matches: 'double-take/matches',
cameras: 'double-take/cameras',
homeassistant: 'homeassistant'
},
host: '192.168.86.101',
user: '',
password: ''
},
logs: { level: 'silly' },
ui: {
path: '',
theme: 'bootstrap4-dark-blue',
editor: { theme: 'nord_dark' },
logs: { lines: 500 },
pagination: { limit: 50 },
thumbnails: { quality: 95, width: 500 }
},
detectors: {
compreface: {
det_prob_threshold: 0.8,
timeout: 15,
url: 'http://192.168.86.102:8000',
key: '*****'
}
},
server: { port: 3000 },
storage: {
path: '/config/double-take',
config: { path: '/config/double-take' },
secrets: { path: '/config', extension: 'yaml' },
media: { path: '/media/double-take' },
tmp: { path: '/dev/shm/double-take' }
},
version: '1.7.0-bf3e911'
}

Supervisor log with Watchdog enabled:

22-03-04 12:35:01 INFO (SyncWorker_3) [supervisor.docker.addon] Starting Docker add-on c7657554/amd64-addon-double-take with version 1.7.0
22-03-04 12:35:33 ERROR (SyncWorker_5) [supervisor.docker.interface] Container addon_c7657554_double-take is not running
22-03-04 12:35:33 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with c7657554_double-take!
22-03-04 12:35:33 INFO (SyncWorker_5) [supervisor.docker.interface] Cleaning addon_c7657554_double-take application
22-03-04 12:35:33 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on c7657554/amd64-addon-double-take with version 1.7.0
22-03-04 12:35:47 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.7:3000 ssl:default [Connect call failed ('172.30.33.7', 3000)]
22-03-04 12:36:03 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with c7657554_double-take!
22-03-04 12:36:03 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_c7657554_double-take application
22-03-04 12:36:03 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on c7657554/amd64-addon-double-take with version 1.7.0
22-03-04 12:36:33 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with c7657554_double-take!
22-03-04 12:36:34 INFO (SyncWorker_5) [supervisor.docker.interface] Cleaning addon_c7657554_double-take application

Also, I'm using Frigate NVR Proxy on my main Home Assistant and notice that when I restart Frigate service on my physical Home Assistant server running Frigate NVR and try to open the Frigate NVR Proxy addon too soon, I also get the "502 Bad Gateway" message because Frigate isn't all the way back up yet. I thought it might be worth pointing out that I get the same error. Didn't know if this helps point the issue at Double Take failing to successfully connect to Frigate, since I don't see any clear errors in the log? I've also tried uninstalling and reinstalling Double Take, rebooted all the servers, and no luck anymore.

Thanks

[mofonics]

I am experiencing the same 502 Bad Gateway error.

[kl4ver]

I am experiencing the same 502 Bad Gateway error. Any updates about this? Can I help somehow?

[thundergreen]

you can try this:

[thundergreen]

#173 (comment)

[jakowenko]

#173 (comment)

I will look at the fix and apply it to the add-on repo.

Someone on my Discord said that repo did not fix their bad gateway.

I'm curious for the users who have it. How many are running one of the following add-ons.

Duck DNS
NGNIX
LetsEncrypt

I'm wondering if it has something to do with SSL or a related setting like that.