<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Upgrading 1.64.1 to 1.65.0 never boots]]></title><description><![CDATA[<p dir="auto">I upgraded my FusionAuth instance (self-hosted container) from 1.64.1 to 1.65.0, but the container never starts.<br />
Reading the logs during start up I found the following issue</p>
<pre><code>SQL: SELECT internal_authentication_keys_id FROM instance LIMIT 1"} 
Cause: org.postgresql.util.PSQLException: ERROR: column \"internal_authentication_keys_id\" does not exist"} 
...
...
...
ERROR org.primeframework.mvc.guice.GuiceBootstrap - Unable to start the server. Exception:"}
</code></pre>
<p dir="auto">So the app is clearly expecting a schema change that my database doesn’t have.</p>
<p dir="auto">What’s confusing is:</p>
<p dir="auto">There are no visible migration scripts running during startup<br />
Release notes don’t mention a migration step<br />
But 1.65 clearly assumes this column exists in instance</p>
<p dir="auto">I downloaded the schemas for both versions and instance.internal_authentication_keys does exist on 1.65.0, but not 1.64.1</p>
]]></description><link>https://fusionauth.io/community/forum/topic/3131/upgrading-1-64-1-to-1-65-0-never-boots</link><generator>RSS for Node</generator><lastBuildDate>Mon, 18 May 2026 23:10:20 GMT</lastBuildDate><atom:link href="https://fusionauth.io/community/forum/topic/3131.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 08 May 2026 10:31:27 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Upgrading 1.64.1 to 1.65.0 never boots on Mon, 18 May 2026 07:12:22 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/2507">@mark-robustelli</a> I haven't tested it again since, but I build a docker image using the base fusionauth image (fusionauth/fusionauth-app) because I have a custom plugin and kickstart file.<br />
So my upgrade process is simply to update the base fusionauth image in my dockerfile, and then update my container in Azure. This has worked fine since 1.56, and updated through all the updates with migrations.<br />
Edit: I just noticed that the downloaded schemas does contain a migration for 1.65, and running it on the database does make the container start now. Would have expected this migration to run on start up like the other updates though.</p>
]]></description><link>https://fusionauth.io/community/forum/post/8600</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/8600</guid><dc:creator><![CDATA[mqwirtnuf]]></dc:creator><pubDate>Mon, 18 May 2026 07:12:22 GMT</pubDate></item><item><title><![CDATA[Reply to Upgrading 1.64.1 to 1.65.0 never boots on Fri, 15 May 2026 14:28:32 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://fusionauth.io/community/forum/uid/3817">@mqwirtnuf</a> How's it going? Can you share your upgrade process?</p>
]]></description><link>https://fusionauth.io/community/forum/post/8599</link><guid isPermaLink="true">https://fusionauth.io/community/forum/post/8599</guid><dc:creator><![CDATA[mark.robustelli]]></dc:creator><pubDate>Fri, 15 May 2026 14:28:32 GMT</pubDate></item></channel></rss>