nezhahq.github.io/assets/en_US_guide_loginq.md.NUiL2A0V.js

import{_ as e,c as a,o,a4 as t}from"./chunks/framework.BmdFiWrL.js";const p=JSON.parse('{"title":"FAQ about logging into the Dashboard","description":"","frontmatter":{"outline":"deep"},"headers":[],"relativePath":"en_US/guide/loginq.md","filePath":"en_US/guide/loginq.md","lastUpdated":1724312755000}'),i={name:"en_US/guide/loginq.md"},r=t('<h1 id="faq-about-logging-into-the-dashboard" tabindex="-1">FAQ about logging into the Dashboard <a class="header-anchor" href="#faq-about-logging-into-the-dashboard" aria-label="Permalink to &quot;FAQ about logging into the Dashboard&quot;">​</a></h1><h2 id="stuck-page-connection-refused-long-response-time-after-login-callback" tabindex="-1">Stuck Page/Connection Refused/Long Response Time After Login Callback <a class="header-anchor" href="#stuck-page-connection-refused-long-response-time-after-login-callback" aria-label="Permalink to &quot;Stuck Page/Connection Refused/Long Response Time After Login Callback&quot;">​</a></h2><p>These issues can manifest in various ways, but ultimately the browser cannot display correctly after login.</p><ol><li>Your server cannot connect to Github/Gitee, which is most common when configuring Github on servers in mainland China. You may try several times or switch to Cloudflare Access.</li><li>You have configured the callback address incorrectly. Ensure that your callback address is correct and that both the <strong>port and protocol</strong> are accurate!</li><li>An unknown error occurred on the Dashboard. You can use a script to check the logs.</li></ol><div class="tip custom-block"><p class="custom-block-title">TIP</p><p>What is a protocol? In the browser, the string that ends your domain with <code>://</code> is the protocol, usually <code>http</code> or <code>https</code>. Since there may be multiple protocol+domain+port combinations available for accessing the Dashboard in a normal deployment, make sure to choose the most appropriate one as the callback.</p></div><h3 id="how-to-check-if-my-callback-address-is-wrong" tabindex="-1">How to Check if My Callback Address is Wrong? <a class="header-anchor" href="#how-to-check-if-my-callback-address-is-wrong" aria-label="Permalink to &quot;How to Check if My Callback Address is Wrong?&quot;">​</a></h3><p>Ensure that the protocol+domain+port displayed in the browser before login and after the callback are consistent.<br> Ensure that your path is <code>/oauth2/callback</code>, <strong>all in lowercase</strong>.</p><h2 id="errors-after-logging-into-the-admin-panel" tabindex="-1">Errors After Logging into the Admin Panel <a class="header-anchor" href="#errors-after-logging-into-the-admin-panel" aria-label="Permalink to &quot;Errors After Logging into the Admin Panel&quot;">​</a></h2><h3 id="http-named-cookie-not-present" tabindex="-1">http: named cookie not present <a class="header-anchor" href="#http-named-cookie-not-present" aria-label="Permalink to &quot;http: named cookie not present&quot;">​</a></h3><ol><li>Clear cookies and log in again, or try a different browser.</li><li>Check the callback address to ensure it is correct and that both the <strong>port and protocol</strong> are accurate! The address initiating the request must be in the same domain as the callback address, with the port, protocol, and domain (or IP) all matching.</li></ol><h3 id="lookup-xxx" tabindex="-1">lookup xxx <a class="header-anchor" href="#lookup-xxx" aria-label="Permalink to &quot;lookup xxx&quot;">​</a></h3><p>The container DNS resolution failed, usually due to modified iptables configurations.<br> It is recommended to restart Docker first, <code>sudo systemctl restart docker</code>, then restart the Dashboard using the script.<br> If the lookup error persists, check if there are other tools controlling iptables, such as firewall.<br> This issue might also be related to the kernel, so try switching to the official kernel.</p><h3 id="invalid-authorization-method-or-the-login-callback-address-is-invalid-expired-or-has-been-revoked" tabindex="-1">Invalid authorization method, or the login callback address is invalid, expired, or has been revoked <a class="header-anchor" href="#invalid-authorization-method-or-the-login-callback-address-is-invalid-expired-or-has-been-revoked" aria-label="Permalink to &quot;Invalid authorization method, or the login callback address is invalid, expired, or has been revoked&quot;">​</a></h3><p>This issue appears only when using Gitee login, and the reason is unclear. Switching to GitHub is recommended.</p><h3 id="oauth2-server-response-missing-access-token" tabindex="-1">oauth2: server response missing access_token <a class="header-anchor" href="#oauth2-server-response-missing-access-token" aria-label="Permalink to &quot;oauth2: server response missing access_token&quot;">​</a></h3><p>This could be caused by various factors, most likely a network issue. Check your network and try again.<br> If unresolved, switching to Github or another method is recommended.</p><h3 id="the-user-is-not-an-admin-of-this-site-and-cannot-log-in" tabindex="-1">The user is not an admin of this site and cannot log in <a class="header-anchor" href="#the-user-is-not-an-admin-of-this-site-and-cannot-log-in" aria-label="Permalink to &quot;The user is not an admin of this site and cannot log in&quot;">​</a></h3><p>You logged in with the wrong account or configured the wrong username. Note that <strong>the username is not an email</strong>, and you can use a script to modify it.<br> For Cloudflare Access users, note that your username is not an email but a User ID.</p><h3 id="dial-tcp-xxx-443-i-o-timeout" tabindex="-1">dial tcp xxx:443 i/o timeout <a class="header-anchor" href="#dial-tcp-xxx-443-i-o-timeout" aria-label="Permalink to &quot;dial tcp xxx:443 i/o timeout&quot;">​</a></h3><p>This is a network issue. Try restarting Docker first, <code>sudo systemctl restart docker</code>, then restart the Dashboard using the script.<br> If you are configuring Github login on a server in mainland China, switching to Cloudflare Access is recommended to avoid network interference.</p><h3 id="net-http-tls-handshake-timeout" tabindex="-1">net/http: TLS handshake timeout <a class="header-anchor" href="#net-http-tls-handshake-timeout" aria-label="Permalink to &quot;net/http: TLS handshake timeout&quot;">​</a></h3><p>Same as above.</p><h3 id="unable-to-receive-email-verification-codes-using-cloudflare-access-as-an-oauth2-provider" tabindex="-1">Unable to receive email verification codes using Cloudflare Access as an OAuth2 Provider <a class="header-anchor" href="#unable-to-receive-email-verification-codes-using-cloudflare-access-as-an-oauth2-provider" aria-label="Permalink to &quot;Unable to receive email verification codes using Cloudflare Access as an OAuth2 Provider&quot;">​</a></h3><ul><li>Ensure that the email verification policy has been correctly configured in <code>Policies</code>.</li><li>Verify that the email address you provided is correct. Note that email addresses not on the policy whitelist will not receive verification codes.</li></ul>',24),n=[r];function s(l,c,h,d,u,g){return o(),a("div",null,n)}const b=e(i,[["render",s]]);export{p as __pageData,b as default};