Creating New Slack bot


I've been trying to set up a slack integration and have followed the steps in the Metabase doc. There is no detailed error message but I am only getting Looks like we ran into some problems on both Metabot On/Off. The message appears right after click on "save changes" button. (so not able to save)

Thanks for your help in advance.

Here is the log (token is masked.):
[5e3ded28-6374-4048-b34c-c7f9775239b5] 2021-05-26T11:06:20-07:00 DEBUG metabase.server.middleware.log PUT /api/slack/settings 400 7.4 ms (0 DB calls)
{:url "",
{:token "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
:limit 1,
:exclude_archived true,
:types "public_channel,private_channel"},
:as :stream,
:conn-timeout 10000,
:socket-timeout 10000}}

Diagnostic info:
"browser-info": {
"language": "en-US",
"platform": "MacIntel",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36",
"vendor": "Google Inc."
"system-info": {
"file.encoding": "UTF-8",
"": "Java(TM) SE Runtime Environment",
"java.runtime.version": "1.8.0_45-b14",
"java.vendor": "Oracle Corporation",
"java.vendor.url": "",
"java.version": "1.8.0_45",
"": "Java HotSpot(TM) 64-Bit Server VM",
"java.vm.version": "25.45-b02",
"": "Linux",
"os.version": "",
"user.language": "en",
"user.timezone": "Zulu"
"metabase-info": {
"databases": [
"hosting-env": "unknown",
"application-database": "mysql",
"application-database-details": {
"database": {
"name": "MySQL",
"version": "5.7.29-32-log"
"jdbc-driver": {
"name": "MariaDB Connector/J",
"version": "2.6.2"
"run-mode": "prod",
"version": {
"tag": "v0.38.1",
"date": "2021-03-03",
"branch": "release-x.38.x",
"hash": "79ef63a"
"settings": {
"report-timezone": null

Hi @fkojima

I'm fairly sure it's caused by your really old version of Java - upgrade:

Otherwise check outgoing firewalls and proxies, and make sure that you can make a connection to from the server where Metabase is running.

And latest release of Metabase is 0.39.2:

Thank you for your quick reply.
We found an issue on the port from our server to It should be resolved by fixing it :slight_smile: