You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, 403 is an authentication/authorization error and Glance itself doesn't have any endpoints that can return that kind of status code, so the issue is likely related to Cloudflare Tunnel's configuration or something else that gets hit before Glance.
As for the host and base-url options, leaving them both blank should suffice in your case. You only need to specify host if you want to limit access to a specific interface, and you only need to specify the base-url if your instance is hosted under a directory rather than a subdomain, such as https://my.domain.com/glance.
Oye, 403 es un error de autenticación/autorización y Glance en sí no tiene ningún punto final que pueda devolver ese tipo de código de estado, por lo que el problema probablemente esté relacionado con la configuración de Cloudflare Tunnel o algo más que se detecta antes que Glance.
En cuanto a la host y base-url opciones, dejarlas en blanco debería ser suficiente en su caso. Sólo necesitas especificar host si desea limitar el acceso a una interfaz específica y solo necesita especificar el base-url si su instancia está alojada en un directorio en lugar de un subdominio, como https://my.domain.com/glance.
I understand. I appreciate your comments. I will check my Cloudflare configuration, in case I have forgotten something.
I have a problem with Cloudflare.
My case is that I have self-hosted the Glance server, behind a Cloudflare Tunnel, so I get a 403 error.
I was wondering if the problem could be the correct host and base-url configuration for a Cloudflare subdomain of this style:
https://my.domain.com
Has anyone had this problem?
How would be the host and base-url configuration?
The text was updated successfully, but these errors were encountered: