Error at https metabase jar niginx openssl java15 windows 10

1

#niginx.conf file

server {
listen 443 ssl;
server_name server1;
ssl_certificate cert.key;
ssl_certificate cert.crt;
ssl_ciphers HIGH:!aNULL:!MD5;
location /api/embed/ {
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $http_host;
proxy_pass http://server1:3030/;
proxy_redirect off;
proxy_read_timeout 240s;
}
}
------------------------------------------------------- I
The metabase is running on server1 at http port set as 3030
Note; In metabse it is http. The url is server1:3030
I am using metabase.jar. Running the command such as
set MB_JETTY_PORT=3030
java -jar metabase.jar

Now at the browser entry of https://server1
results in ssl record long .... ssl error at the browser,

My environment is
Windows 10.
The java version is 15.
At the host file there is an entry with IPaddress server1

Similar doubts in this forum the kind of answer recommended is to ask the help of web app developers. I am a web app developer. Another answers are Ubuntu based solutions. I may not able to go for commercial license. So this topic.
Any mistake I am doing here at setting Metabase server. Any help thanks in advance.

2

Can you post which ssl error you’re seeing? Also use Java 11

1 Like
3

Ssl error I solved. It was a mistake. The port number was removed in the server name at the React Application. My server name is dtsc.
So ssl error went off.
Now Firefox browser says can not open the page "To protect your security, dtsc will not allow Firefox to display the page if another site has embedded it. To see this page, you need to open it in a new window.
It tells content Security Policy: The page’s settings blocked the loading of a resource at https://dtsc/revenue
Content Security Policy: The page’s settings blocked the loading of a resource at https://dtsc/revenue (“frame-ancestors”).
As instructed java 11 is being used. The 3030 is the port I am running metabase. Windows 10 OS. My React app works in port 3000. Nginx used to set the https with self signed certificates.
Any were I doing any mistake.