Suggestion: Auto update site URL while upgrading from v3.1.x to v3.2.x

[issonia-ma]

When upgrading TeamPass 3.1.7.6 to 3.2.x following official Nginx setup, migration does not update the site URL stored in database.
Old URL contains /teampass , all AJAX requests get 404 and user data cannot display.
Could you add an SQL statement to automatically remove /teampass during migration?

[nilsteampassnet]

Thanks for the report, you're right that the URL is the problem, and I've fixed it in develop.

I didn't go with a plain /teampass removal though: many installations legitimately stay under a sub-path (Apache alias, reverse proxy), and stripping it unconditionally would break them. The actual bug is elsewhere: the upgrade wizard already asks for the "Full URL to TeamPass" in step 1 and pre-fills it with the URL it is actually running from, it just never saved that value to the database.
It now does, before the version scripts run, and settings derived from it (favicon, files URL) follow along when they still carry the old URL.
So an instance moved from /teampass to the web root gets the right URL automatically, and one that stays under /teampass keeps it.

I also added a health check (Utilities → Health) that flags a stored URL whose path doesn't match the one the page is served from, so the cause is visible instead of showing up as unexplained 404s.

In the meantime, on an already-upgraded instance you can fix it directly: Settings → URL to TeamPass.
That page saves through relative URLs, so it still works even while the stored URL is wrong.