new deploy: 2022-05-16T09:03:39+00:00
parent
95110fb70a
commit
c7e83224ba
|
|
@ -51,11 +51,11 @@
|
|||
</content>
|
||||
</entry>
|
||||
<entry xml:lang="en">
|
||||
<title>Troubleshooting Gitea upgrades showcase</title>
|
||||
<title>[solved] blank or error 500 page after login</title>
|
||||
<published>2022-05-08T00:00:00+00:00</published>
|
||||
<updated>2022-05-08T00:00:00+00:00</updated>
|
||||
<link href="https://hostea.org/blog/upgrades-01/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/upgrades-01/</id>
|
||||
<link href="https://hostea.org/blog/blank-or-error-500-page-after-login/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/blank-or-error-500-page-after-login/</id>
|
||||
<content type="html"><p>The <a href="https://docs.gitea.io/en-us/upgrade-from-gitea/#upgrade-from-binary">instructions to upgrade a Gitea instance</a> only require three to four steps. They work fine most of the time but the documentation is lacking a &quot;Troubleshooting&quot; section to help out when something goes wrong. Maintaining instructions on how to diagnose and fix upgrade problems is an ambitious undertaking and requires updates every time a new case is discovered.</p>
|
||||
<p>An <a href="https://forum.hostea.org/t/things-to-know-about-gitea-upgrades/39">inventory of the known upgrade issues</a> was started to figure out how to structure such a section in the documentation. The <a href="https://blog.gitea.io/">release notes</a> were analyzed all the way back to <a href="https://github.com/go-gitea/gitea/releases/tag/v1.9.6">Gitea 1.9.6</a> and the work is still in progress. Here is a sample of the tips that will be included:</p>
|
||||
<ul>
|
||||
|
|
|
|||
|
|
@ -33,21 +33,21 @@
|
|||
<meta name="referrer" content="no-referrer-when-downgrade" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
|
||||
<title>Troubleshooting Gitea upgrades showcase | Hostea: Managed Gitea Hosting </title>
|
||||
<title>[solved] blank or error 500 page after login | Hostea: Managed Gitea Hosting </title>
|
||||
<meta name="referrer" content="no-referrer-when-downgrade" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
|
||||
<meta name="description" content="After going to production, some Gitea users saw a blank page after login and had to manually type the URL of the project they wanted to see in the browser." />
|
||||
|
||||
|
||||
<meta property="og:title" content="Troubleshooting Gitea upgrades showcase | Hostea: Managed Gitea Hosting " />
|
||||
<meta property="og:title" content="[solved] blank or error 500 page after login | Hostea: Managed Gitea Hosting " />
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="https://hostea.org" />
|
||||
|
||||
<meta property="og:description" content="After going to production, some Gitea users saw a blank page after login and had to manually type the URL of the project they wanted to see in the browser." />
|
||||
<meta
|
||||
property="og:site_name"
|
||||
content="Troubleshooting Gitea upgrades showcase | Hostea: Managed Gitea Hosting "
|
||||
content="[solved] blank or error 500 page after login | Hostea: Managed Gitea Hosting "
|
||||
/>
|
||||
<link
|
||||
rel="apple-touch-icon"
|
||||
|
|
@ -197,7 +197,7 @@
|
|||
|
||||
|
||||
<div class="page__container">
|
||||
<h1 class="page__group-title">Troubleshooting Gitea upgrades showcase</h1>
|
||||
<h1 class="page__group-title">[solved] blank or error 500 page after login</h1>
|
||||
<p class="blog__post-meta">
|
||||
|
||||
|
||||
|
|
@ -241,8 +241,8 @@
|
|||
</li>
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/upgrades-01/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">Troubleshooting Gitea upgrades showcase</h2>
|
||||
<a href="https://hostea.org/blog/blank-or-error-500-page-after-login/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">[solved] blank or error 500 page after login</h2>
|
||||
<p class="blog__post-meta">
|
||||
|
||||
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -10,12 +10,12 @@
|
|||
<loc>https://hostea.org/blog/</loc>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://hostea.org/blog/project-plans-for-hosted-gitea-online-service/</loc>
|
||||
<lastmod>2022-04-18</lastmod>
|
||||
<loc>https://hostea.org/blog/blank-or-error-500-page-after-login/</loc>
|
||||
<lastmod>2022-05-08</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://hostea.org/blog/upgrades-01/</loc>
|
||||
<lastmod>2022-05-08</lastmod>
|
||||
<loc>https://hostea.org/blog/project-plans-for-hosted-gitea-online-service/</loc>
|
||||
<lastmod>2022-04-18</lastmod>
|
||||
</url>
|
||||
<url>
|
||||
<loc>https://hostea.org/blog/upgrades/</loc>
|
||||
|
|
|
|||
|
|
@ -51,11 +51,11 @@
|
|||
</content>
|
||||
</entry>
|
||||
<entry xml:lang="en">
|
||||
<title>Troubleshooting Gitea upgrades showcase</title>
|
||||
<title>[solved] blank or error 500 page after login</title>
|
||||
<published>2022-05-08T00:00:00+00:00</published>
|
||||
<updated>2022-05-08T00:00:00+00:00</updated>
|
||||
<link href="https://hostea.org/blog/upgrades-01/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/upgrades-01/</id>
|
||||
<link href="https://hostea.org/blog/blank-or-error-500-page-after-login/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/blank-or-error-500-page-after-login/</id>
|
||||
<content type="html"><p>The <a href="https://docs.gitea.io/en-us/upgrade-from-gitea/#upgrade-from-binary">instructions to upgrade a Gitea instance</a> only require three to four steps. They work fine most of the time but the documentation is lacking a &quot;Troubleshooting&quot; section to help out when something goes wrong. Maintaining instructions on how to diagnose and fix upgrade problems is an ambitious undertaking and requires updates every time a new case is discovered.</p>
|
||||
<p>An <a href="https://forum.hostea.org/t/things-to-know-about-gitea-upgrades/39">inventory of the known upgrade issues</a> was started to figure out how to structure such a section in the documentation. The <a href="https://blog.gitea.io/">release notes</a> were analyzed all the way back to <a href="https://github.com/go-gitea/gitea/releases/tag/v1.9.6">Gitea 1.9.6</a> and the work is still in progress. Here is a sample of the tips that will be included:</p>
|
||||
<ul>
|
||||
|
|
|
|||
|
|
@ -238,8 +238,8 @@
|
|||
</li>
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/upgrades-01/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">Troubleshooting Gitea upgrades showcase</h2>
|
||||
<a href="https://hostea.org/blog/blank-or-error-500-page-after-login/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">[solved] blank or error 500 page after login</h2>
|
||||
<p class="blog__post-meta">
|
||||
8
|
||||
May
|
||||
|
|
|
|||
|
|
@ -51,11 +51,11 @@
|
|||
</content>
|
||||
</entry>
|
||||
<entry xml:lang="en">
|
||||
<title>Troubleshooting Gitea upgrades showcase</title>
|
||||
<title>[solved] blank or error 500 page after login</title>
|
||||
<published>2022-05-08T00:00:00+00:00</published>
|
||||
<updated>2022-05-08T00:00:00+00:00</updated>
|
||||
<link href="https://hostea.org/blog/upgrades-01/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/upgrades-01/</id>
|
||||
<link href="https://hostea.org/blog/blank-or-error-500-page-after-login/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/blank-or-error-500-page-after-login/</id>
|
||||
<content type="html"><p>The <a href="https://docs.gitea.io/en-us/upgrade-from-gitea/#upgrade-from-binary">instructions to upgrade a Gitea instance</a> only require three to four steps. They work fine most of the time but the documentation is lacking a &quot;Troubleshooting&quot; section to help out when something goes wrong. Maintaining instructions on how to diagnose and fix upgrade problems is an ambitious undertaking and requires updates every time a new case is discovered.</p>
|
||||
<p>An <a href="https://forum.hostea.org/t/things-to-know-about-gitea-upgrades/39">inventory of the known upgrade issues</a> was started to figure out how to structure such a section in the documentation. The <a href="https://blog.gitea.io/">release notes</a> were analyzed all the way back to <a href="https://github.com/go-gitea/gitea/releases/tag/v1.9.6">Gitea 1.9.6</a> and the work is still in progress. Here is a sample of the tips that will be included:</p>
|
||||
<ul>
|
||||
|
|
|
|||
|
|
@ -238,8 +238,8 @@
|
|||
</li>
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/upgrades-01/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">Troubleshooting Gitea upgrades showcase</h2>
|
||||
<a href="https://hostea.org/blog/blank-or-error-500-page-after-login/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">[solved] blank or error 500 page after login</h2>
|
||||
<p class="blog__post-meta">
|
||||
8
|
||||
May
|
||||
|
|
|
|||
|
|
@ -51,11 +51,11 @@
|
|||
</content>
|
||||
</entry>
|
||||
<entry xml:lang="en">
|
||||
<title>Troubleshooting Gitea upgrades showcase</title>
|
||||
<title>[solved] blank or error 500 page after login</title>
|
||||
<published>2022-05-08T00:00:00+00:00</published>
|
||||
<updated>2022-05-08T00:00:00+00:00</updated>
|
||||
<link href="https://hostea.org/blog/upgrades-01/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/upgrades-01/</id>
|
||||
<link href="https://hostea.org/blog/blank-or-error-500-page-after-login/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/blank-or-error-500-page-after-login/</id>
|
||||
<content type="html"><p>The <a href="https://docs.gitea.io/en-us/upgrade-from-gitea/#upgrade-from-binary">instructions to upgrade a Gitea instance</a> only require three to four steps. They work fine most of the time but the documentation is lacking a &quot;Troubleshooting&quot; section to help out when something goes wrong. Maintaining instructions on how to diagnose and fix upgrade problems is an ambitious undertaking and requires updates every time a new case is discovered.</p>
|
||||
<p>An <a href="https://forum.hostea.org/t/things-to-know-about-gitea-upgrades/39">inventory of the known upgrade issues</a> was started to figure out how to structure such a section in the documentation. The <a href="https://blog.gitea.io/">release notes</a> were analyzed all the way back to <a href="https://github.com/go-gitea/gitea/releases/tag/v1.9.6">Gitea 1.9.6</a> and the work is still in progress. Here is a sample of the tips that will be included:</p>
|
||||
<ul>
|
||||
|
|
|
|||
|
|
@ -238,8 +238,8 @@
|
|||
</li>
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/upgrades-01/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">Troubleshooting Gitea upgrades showcase</h2>
|
||||
<a href="https://hostea.org/blog/blank-or-error-500-page-after-login/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">[solved] blank or error 500 page after login</h2>
|
||||
<p class="blog__post-meta">
|
||||
8
|
||||
May
|
||||
|
|
|
|||
|
|
@ -51,11 +51,11 @@
|
|||
</content>
|
||||
</entry>
|
||||
<entry xml:lang="en">
|
||||
<title>Troubleshooting Gitea upgrades showcase</title>
|
||||
<title>[solved] blank or error 500 page after login</title>
|
||||
<published>2022-05-08T00:00:00+00:00</published>
|
||||
<updated>2022-05-08T00:00:00+00:00</updated>
|
||||
<link href="https://hostea.org/blog/upgrades-01/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/upgrades-01/</id>
|
||||
<link href="https://hostea.org/blog/blank-or-error-500-page-after-login/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/blank-or-error-500-page-after-login/</id>
|
||||
<content type="html"><p>The <a href="https://docs.gitea.io/en-us/upgrade-from-gitea/#upgrade-from-binary">instructions to upgrade a Gitea instance</a> only require three to four steps. They work fine most of the time but the documentation is lacking a &quot;Troubleshooting&quot; section to help out when something goes wrong. Maintaining instructions on how to diagnose and fix upgrade problems is an ambitious undertaking and requires updates every time a new case is discovered.</p>
|
||||
<p>An <a href="https://forum.hostea.org/t/things-to-know-about-gitea-upgrades/39">inventory of the known upgrade issues</a> was started to figure out how to structure such a section in the documentation. The <a href="https://blog.gitea.io/">release notes</a> were analyzed all the way back to <a href="https://github.com/go-gitea/gitea/releases/tag/v1.9.6">Gitea 1.9.6</a> and the work is still in progress. Here is a sample of the tips that will be included:</p>
|
||||
<ul>
|
||||
|
|
|
|||
|
|
@ -238,8 +238,8 @@
|
|||
</li>
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/upgrades-01/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">Troubleshooting Gitea upgrades showcase</h2>
|
||||
<a href="https://hostea.org/blog/blank-or-error-500-page-after-login/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">[solved] blank or error 500 page after login</h2>
|
||||
<p class="blog__post-meta">
|
||||
8
|
||||
May
|
||||
|
|
|
|||
|
|
@ -51,11 +51,11 @@
|
|||
</content>
|
||||
</entry>
|
||||
<entry xml:lang="en">
|
||||
<title>Troubleshooting Gitea upgrades showcase</title>
|
||||
<title>[solved] blank or error 500 page after login</title>
|
||||
<published>2022-05-08T00:00:00+00:00</published>
|
||||
<updated>2022-05-08T00:00:00+00:00</updated>
|
||||
<link href="https://hostea.org/blog/upgrades-01/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/upgrades-01/</id>
|
||||
<link href="https://hostea.org/blog/blank-or-error-500-page-after-login/" type="text/html"/>
|
||||
<id>https://hostea.org/blog/blank-or-error-500-page-after-login/</id>
|
||||
<content type="html"><p>The <a href="https://docs.gitea.io/en-us/upgrade-from-gitea/#upgrade-from-binary">instructions to upgrade a Gitea instance</a> only require three to four steps. They work fine most of the time but the documentation is lacking a &quot;Troubleshooting&quot; section to help out when something goes wrong. Maintaining instructions on how to diagnose and fix upgrade problems is an ambitious undertaking and requires updates every time a new case is discovered.</p>
|
||||
<p>An <a href="https://forum.hostea.org/t/things-to-know-about-gitea-upgrades/39">inventory of the known upgrade issues</a> was started to figure out how to structure such a section in the documentation. The <a href="https://blog.gitea.io/">release notes</a> were analyzed all the way back to <a href="https://github.com/go-gitea/gitea/releases/tag/v1.9.6">Gitea 1.9.6</a> and the work is still in progress. Here is a sample of the tips that will be included:</p>
|
||||
<ul>
|
||||
|
|
|
|||
|
|
@ -238,8 +238,8 @@
|
|||
</li>
|
||||
|
||||
<li class="blog__post-item">
|
||||
<a href="https://hostea.org/blog/upgrades-01/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">Troubleshooting Gitea upgrades showcase</h2>
|
||||
<a href="https://hostea.org/blog/blank-or-error-500-page-after-login/" class="blog__post-link">
|
||||
<h2 class="blog__post-title">[solved] blank or error 500 page after login</h2>
|
||||
<p class="blog__post-meta">
|
||||
8
|
||||
May
|
||||
|
|
|
|||
Loading…
Reference in New Issue