# Only HTTP works but not HTTPS for Allowed Callback/Logout URLs

**URL:** <https://community.auth0.com/t/only-http-works-but-not-https-for-allowed-callback-logout-urls/145569>\
**Category:** Get Help\
**Tags:** configuration, application\
**Created:** [September 6, 2024, 10:04pm UTC](https://community.auth0.com/t/only-http-works-but-not-https-for-allowed-callback-logout-urls/145569 "2024-09-06T22:04:33Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![acecauis](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/acecauis/32/20470_2.png) [@acecauis](https://community.auth0.com/u/acecauis)\
**Post date:** [September 6, 2024, 10:04pm UTC](https://community.auth0.com/t/only-http-works-but-not-https-for-allowed-callback-logout-urls/145569/1 "2024-09-06T22:04:33Z")

</div>

In our Application URIs settings, I am not sure why our domain’s URL only works with HTTP and not HTTPS.

Previously, when using HTTPS,

```auto
https://canpersonalitychange.com

```

Auth0 would throw the `Callback URL Mismatch.` error and complain that the callback URL was set to `http://canpersonalitychange.com`.  
Even after changing the callback and logout URLs to use HTTPS, and the `AUTH0_BASE_URL` to also use HTTPS, the application logs would still say that `http://canpersonalitychange.com` was being used.

Even more strange, after changed the callback and logout URLs to be something completely different, Auth0 would still throw the `Callback URL Mismatch.` error and in the logs I would see that the URL `http://canpersonalitychange.com` was incorrectly being used.

Thus, I am no sure how to resolve this issue given that Auth0 only seems to use the HTTP URL, `http://canpersonalitychange.com`, and not the HTTPS URL, even after I reconfigure my callback URL and logout URL to use `https://canpersonalitychange.com`.

Please help!

---

<div class="post-metadata">

**Author:** ![acecauis](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/acecauis/32/20470_2.png) [@acecauis](https://community.auth0.com/u/acecauis)\
**Post date:** [September 21, 2024, 6:34pm UTC](https://community.auth0.com/t/only-http-works-but-not-https-for-allowed-callback-logout-urls/145569/2 "2024-09-21T18:34:14Z")

</div>

It has been more than 2 weeks.  
Can I please get some eyes on this request for help!

This isn’t a blocker, but my other [support request](https://community.auth0.com/t/deleting-a-user-from-custom-database-does-not-delete-user-from-applications-list-of-users/145574) absolutely is a blocker, and I have not received even a reply on that post either!

---

<div class="post-metadata">

**Author:** ![brdavid](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/brdavid/32/70958_2.png) [@brdavid](https://community.auth0.com/u/brdavid)\
**Post date:** [January 20, 2025, 3:49pm UTC](https://community.auth0.com/t/only-http-works-but-not-https-for-allowed-callback-logout-urls/145569/3 "2025-01-20T15:49:08Z")

</div>

I would love an answer to this as well as I am running into this same issue.

---

<div class="post-metadata">

**Author:** ![nik.baleca](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/nik.baleca/32/68749_2.png) [@nik.baleca](https://community.auth0.com/u/nik.baleca)\
**Post date:** [January 21, 2025, 11:39pm UTC](https://community.auth0.com/t/only-http-works-but-not-https-for-allowed-callback-logout-urls/145569/4 "2025-01-21T23:39:02Z")

</div>

Hi @acecauis

Thank you for posting regarding the issue that you are facing with your callback URLs.  
I am sorry about the late reply to your inquiry.

As far as I have checked on your tenant, the **Allowed Callback URLs** and **Allow Login URLs** still seem to be under `http://` instead of `https://`.

You can also check that your login request does not parse a different URL for the `redirect_uri` than the one expected in the **Callback URL**. I recommend checking your `/authorize` request, specifically the `redirect_uri` query parameter, to make sure the URL points to the URL specified in your Allowed Callback URLs of your Application’s settings

As an alternative, you can attempt to force the **HTTPS** as follows:

```auto
HttpContext.Request.IsHttps = true;
await HttpContext.ChallengeAsync(Auth0Constants.AuthenticationScheme, authenticationProperties);

```

Otherwise, if you are still facing issues with your page being redirected to the wrong URL while using custom domains, please review this [Knowledge Article](https://community.auth0.com/t/troubleshooting-custom-domain-certificate-errors/120911) regarding possible issues with certificates.

If you are still having an issue or any other questions, feel free to reply back to this post.

Kind Regards,  
Nik

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [February 4, 2025, 11:39pm UTC](https://community.auth0.com/t/only-http-works-but-not-https-for-allowed-callback-logout-urls/145569/5 "2025-02-04T23:39:24Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
