Socket fail to connect to host:localhost, port:34267. Connection refused (Connection refused)

Get Help
1

Can someone help me with this error

There was a problem with your question

Most of the time this is caused by an invalid selection or bad input value. Double check your inputs and retry your query.

Show error details

Here’s the full error message

Socket fail to connect to host:localhost, port:34267. Connection refused (Connection refused)

2

Hi @David_St
Post “Diagnostic Info” from Admin > Troubleshooting.
You are likely seeing this issue - upvote by clicking :+1: on the first post of the issue:
https://github.com/metabase/metabase/issues/6114
https://github.com/metabase/metabase/issues/3941

5

{
“browser-info”: {
“language”: “en-US”,
“platform”: “Win32”,
“userAgent”: “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.104 Safari/537.36”,
“vendor”: “Google Inc.”
},
“system-info”: {
“file.encoding”: “UTF-8”,
“java.runtime.name”: “OpenJDK Runtime Environment”,
“java.runtime.version”: “11.0.7+10”,
“java.vendor”: “AdoptOpenJDK”,
“java.vendor.url”: “https://adoptopenjdk.net/”,
“java.version”: “11.0.7”,
“java.vm.name”: “OpenJDK 64-Bit Server VM”,
“java.vm.version”: “11.0.7+10”,
“os.name”: “Linux”,
“os.version”: “3.10.0-1127.19.1.el7.x86_64”,
“user.language”: “en”,
“user.timezone”: “GMT”
},
“metabase-info”: {
“databases”: [
“mysql”
],
“hosting-env”: “unknown”,
“application-database”: “h2”,
“application-database-details”: {
“database”: {
“name”: “H2”,
“version”: “1.4.197 (2018-03-18)”
},
“jdbc-driver”: {
“name”: “H2 JDBC Driver”,
“version”: “1.4.197 (2018-03-18)”
}
},
“run-mode”: “prod”,
“version”: {
“date”: “2021-01-20”,
“tag”: “v0.37.7”,
“branch”: “release-x.37.x”,
“hash”: “2b034aa”
},
“settings”: {
“report-timezone”: null
}
}
}

6

Dear flamber can you help now. i posted the diagnostic info

7

@David_St

  1. Migrate away from H2:
    https://www.metabase.com/docs/latest/operations-guide/migrating-from-h2.html
  2. The workaround is to setup the tunnel manually instead of using the built-in tunnel in Metabase:
    https://www.metabase.com/docs/latest/administration-guide/01-managing-databases.html#what-if-the-built-in-ssh-tunnels-dont-fit-my-needs
8

Dear Flamber
I did a port forwarding of 443 to 8081 can it cause the issues. As before forwarding when we set up metabase it was working efficiently.

Thanks
Dave

9

can you get me a tutorial to migrate from H2 using docker.

10

@David_St Copy the H2 file (/application.db/metabase.db.mv.db) out and do it outside - it’s a one-time procedure.
This might help you: Run the Migration from H2 to MySQL from inside Docker?
Once you have migrated, then setup a new container that will connect to the new application database:
https://metabase.com/docs/latest/operations-guide/running-metabase-on-docker.html