Admin pages give 404

Everything seems to be running fine with the exception of the Admin pages.

I get the "We're a little lost... The page you asked for couldn't be found." 404 message on the Admin > Settings page.

The Databases and Troubleshooting pages work fine.

I just upgraded to 39.4 from 39.3 and the issue is the same.

Hi @frank
Post "Diagnostic Info" from Admin > Troubleshooting.
There's no 39.4 - latest release is 39.3, which was released a few hours ago.
Please validate that the sha256 checksum of the JAR file matches what is shown on the release page.

Hi @flamber, thanks for the quick reply. My mistake with the versions, you are correct: I upgraded from .2 to .3.

The sha256 of the JAR matches.

Here's the Diagnostic Info

  "browser-info": {
    "language": "en-GB",
    "platform": "Win32",
    "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36",
    "vendor": "Google Inc."
  "system-info": {
    "file.encoding": "UTF-8",
    "": "OpenJDK Runtime Environment",
    "java.runtime.version": "11.0.11+9",
    "java.vendor": "AdoptOpenJDK",
    "java.vendor.url": "",
    "java.version": "11.0.11",
    "": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "11.0.11+9",
    "": "Linux",
    "os.version": "5.4.0-54-generic",
    "user.language": "en",
    "user.timezone": "Europe/Berlin"
  "metabase-info": {
    "databases": [
    "hosting-env": "unknown",
    "application-database": "mysql",
    "application-database-details": {
      "database": {
        "name": "MariaDB",
        "version": "10.3.29-MariaDB-0ubuntu0.20.04.1"
      "jdbc-driver": {
        "name": "MariaDB Connector/J",
        "version": "2.6.2"
    "run-mode": "prod",
    "version": {
      "date": "2021-05-27",
      "tag": "v0.39.3",
      "branch": "release-x.39.x",
      "hash": "598a112"
    "settings": {
      "report-timezone": "Europe/Berlin"


  1. Check the logs for errors - Admin > Troubleshooting > Logs (or the console)
  2. Check the browser developer console for errors
  3. If you downgrade to 0.39.2, does it then work again?
  4. Do you have a reverse-proxy (CDN, cache, etc like Cloudflare)?

Hi @flamber,

The only thing in the logs was this:
WARN metabase.server.middleware.log POST /api/jsonws/invoke 404 1.5 ms (0 DB calls) "API endpoint does not exist."

When I open opened the browser console and refreshed the Settings page, it suddenly reappeared... So problem solved, but not sure how :wink:

Thanks for your help.

PS. Metabase is awesome, keep up the good work!

@frank Then I'm 95% sure that you're using some proxy, which had a cached some of the files used in previous versions and was mixing them together with new versions, which then caused problems.
I have spend soooo many hours debugging proxy problems and they can cause the strangest problems: