nezhahq.github.io/assets/en_US_guide_loginq.md.9b2c983a.js

import{_ as e,o,c as t,R as a}from"./chunks/framework.1625126e.js";const b=JSON.parse('{"title":"","description":"","frontmatter":{},"headers":[],"relativePath":"en_US/guide/loginq.md","filePath":"en_US/guide/loginq.md","lastUpdated":1687190167000}'),r={name:"en_US/guide/loginq.md"},i=a('<h2 id="page-refuses-to-connect-or-timeout-after-login-callback" tabindex="-1">Page refuses to connect or timeout after login callback <a class="header-anchor" href="#page-refuses-to-connect-or-timeout-after-login-callback" aria-label="Permalink to &quot;Page refuses to connect or timeout after login callback&quot;">​</a></h2><ol><li>Your server cannot connect to Github, consider trying several times or switching to Gitlab.</li><li>You have configured the wrong callback URL, make sure your callback URL is correct and <strong>port and protocol</strong> are correct!</li><li>An unknown error occurred in Dashboard, you can use the script to check the logs.</li></ol><div class="tip custom-block"><p class="custom-block-title">TIP</p><p>What is a protocol?<br> In the browser, your domain name ending with <code>://</code> is the protocol, usually <code>http</code> and <code>https</code>. Since the Dashboard may be accessible by multiple protocols + domain + port combinations under normal deployment, please make sure to choose the most appropriate one as the callback.</p></div><h3 id="how-do-i-check-if-my-callback-url-is-wrong" tabindex="-1">How do I check if my callback URL is wrong? <a class="header-anchor" href="#how-do-i-check-if-my-callback-url-is-wrong" aria-label="Permalink to &quot;How do I check if my callback URL is wrong?&quot;">​</a></h3><p>Please make sure the protocol+domain+port displayed by your browser before login and the protocol+domain+port you jump to after login are the same.<br> Please make sure your path is <code>/oauth2/callback</code>, <strong>all lowercase</strong>.</p><h2 id="dashboard-errors-after-login" tabindex="-1">Dashboard errors after login <a class="header-anchor" href="#dashboard-errors-after-login" aria-label="Permalink to &quot;Dashboard errors after login&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><p>Clear your browser cookies and log in again, or change your browser.</p><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>DNS resolution failure, in most cases, is due to iptables-related configuration changes.<br> It is recommended to restart docker first, <code>sudo systemctl restart docker</code>, and then use the script to restart the Dashboard.<br> If the lookup error still occurs, it is recommended to check whether there are other tools to control iptables, such as Aapanel Firewall.<br> This problem may also be related to the kernel, please try to change the official kernel.</p><h3 id="the-authorization-method-is-invalid-or-the-login-callback-url-is-invalid-expired-or-has-been-revoked" tabindex="-1">The authorization method is invalid, or the login callback URL is invalid, expired, or has been revoked <a class="header-anchor" href="#the-authorization-method-is-invalid-or-the-login-callback-url-is-invalid-expired-or-has-been-revoked" aria-label="Permalink to &quot;The authorization method is invalid, or the login callback URL is invalid, expired, or has been revoked&quot;">​</a></h3><p>Suggest changing the authentication method to Github/Gitlab.</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>It may be caused by a number of factors, the most likely is a network problem, we suggest to check the network and retry.<br> If you can&#39;t solve it, we suggest changing the authentication method to Github/Gitlab.</p><h3 id="this-user-is-not-the-administrator-or-cannot-login" tabindex="-1">This user is not the administrator or cannot login <a class="header-anchor" href="#this-user-is-not-the-administrator-or-cannot-login" aria-label="Permalink to &quot;This user is not the administrator or cannot login&quot;">​</a></h3><p>You have logged into the wrong account or configured the wrong username, note that <strong>username is not email</strong>, you can use a script to modify it.</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>If the server has network problems, you can restart docker first, <code>sudo systemctl restart docker</code>, and then use the script to restart the Dashboard.<br> You can also change to another OAuth method if necessary.</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>',20),n=[i];function s(l,c,h,d,u,p){return o(),t("div",null,n)}const k=e(r,[["render",s]]);export{b as __pageData,k as default};