[Solved] 404 on /auth/external/callback

Configuration
1

Firstly my apologies if this has been asked and answered elsewhere but I can’t seem to find any information on this issue.

Home Assistant running on RPI3, access via duckdns I’m trying to set up a zoom presence sensor but i’m falling at the callback. I’m getting a 404 on

xxx.duckdns.org:8123/auth/external/callback
xxx.duckdns.org/auth/external/callback
local-ip:8123/auth/external/callback
local-ip/auth/external/callback

I’ve tried removing the depreciated base_url, specifying internal/external url via web interface and config to no effect. Am I missing something obvious? Is there something I need to enable to use /auth/external/callback ?

2

Hi @johnfegan there must be an issue with your configuration although I can’t tell you what it is. Is your Home Assistant instance accessible from the internet (aka without VPN)? If so, you must use the URL that you would use to access the instance from the internet.

Also, did you add the protocol? HTTP/HTTPS? That is required in the URL defined in the Zoom app

3

Hey Raman, thanks for coming back, yeah it’s accessible externally via duckdns, I’ve got a google integration set up etc. can use the pwa outwith the network etc. HA only resolves over ssl.

Excluding my various integrations sensors/switches/lights etc. (mainly mqtt/zigbee/tasmota all working/validating) config is as below:

http:
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

default_config:
python_script:
frontend:
history:
logbook:
config:

# Text to speech
tts:
  - platform: google_translate

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

Any glaring issues?

4

Nope, so a couple of other follow up questions:

  1. Is your External URL set to the URL you use to access Home Assistant? (I’m assuming that’s either “https://xxx.duckdns.org:8123” or “https://xxx.duckdns.org” depending on whether or not you use a reverse proxy to hide the port)
  2. In the Zoom app, is your callback URL set to “https://xxx.duckdns.org:8123/auth/external/callback” or “https://xxx.duckdns.org/auth/external/callback”? (should match #1)
5

Yeah mate I’m forwarding external 443 - internal 8123, I’ve tried every combination I can think of as detailed above.

I don’t think the issue is on zooms end, as I’m unable to get a valid response on any combination of /auth/external/callback regardless of if I’m using internal or external address, specifying port or not. This would seem to indicate an issue with the HA set up to me but as I say beyond my configurations and a few add ons, which excluding duckdns I’ve disabled one by one to no change I’m pretty vanilla…

6

Sorry if it sounds like I am being pedantic, I am just trying to check all the boxes. And you are in fact including https:// in the Zoom app configuration?

One other thing you can try is to add the following to your config:

homeassistant:
  auth_providers:
  - type: homeassistant
7

I am including https: but as a I say HA 404s when I try to access myself on internal/local so it’s very unlikely the issue has anything to do with what I’m populating in zoom.

I’ve tried specifying auth providers as suggested above, still no change.

8

Same problem here, were you able to resolve this? when I do wget/curl to this url, I simply get 404.
Using the HA docker

9

Same issue for me. HA in docker. I get a 404 if I open auth/external/callback on my browser.

10

No i’ve rolled out a vanilla install and still had the same issue, in the end I lost interest. A shame as it’d be really helpful but above my skillset to debug

1 Like
11

I found this thread having the same issue. I resolved it by insuring the host in the redirect URL http://<your_home_assistant_url_or_local_ip>:/auth/external/callback is the same as the page from which you’re starting the integration. You can have multiple configured in the Spotify application, so you could add both host and IP. I have an internal and external hostname and just happened to have set the wrong ones!

Hope this helps.

12

I’ve since resolved my issue, doesn’t seem to be anything to do with the redirect URL but rather with the HACS install of zoom. I’m still unsure why, though fallowing the latest update I removed zoom, and then reinstalled via HACS, added credentials via yaml and rebooted. I still get an error when trying to access the callback URL, though this time it warns:

Missing code or state parameter in https://xxx.duckdns.org/auth/external/callback?code=code-here

Despite this the binary sensor now works, and is updating my zoom status allowing me to use for automations.

13

Ok, got this solved, this is a classic catch 22, I didn’t have the url since I had no integration using it, and I could not setup the integration because the url did not exist.

For me it was the neato integration that has moved to oauth2.

So, to resolve this, I have added the integration with fake secret and id (just used 1 for both), restarted and the url was no longer 404. Then I created the dev account for neato. and than corrected the id and password. Now things are working. :slight_smile: