I have tried it with RTC 6.0.5 and 6.0.6 but I am pretty sure it would work with other versions as well. So I decided to switch the Eclipse environment to a current JDK and that solved the problem. The answers pointed at version issues and certification mismatches. I searched the internet and was not really sure about a solution still. I had the same issue yesterday with 6.0.5 and 6.0.6 and I knew it was working very recently – when I moved to my new laptop. It does not allow you to proceed and add an exception to connect to the web site. It looks like the usual SSL issue with the standard certificate, but it actually is not. If this keeps happening, try contacting the website’s owner. This might be because the site uses outdated or unsafe TLS security settings. Report errors like this to help Mozilla identify and block malicious sites Please contact the website owners to inform them of this problem.
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Error code: SSL_ERROR_INTERNAL_ERROR_ALERT Peer reports it experienced an internal error. This site can’t provide a secure connection localhost sent an invalid response.Īn error occurred during a connection to localhost:7443. However, if you try to follow the description in the Extensions Workshop and you try to connect with a browser to see a screen like the one below. You can even connect with an Eclipse client to the server. When launching the Jetty Debug server, everything seems to be fine. Problem: the browser prevents connecting to the Jetty server Today a colleague saw the same and asked for help. I was not able to find a solution so far. Since some time now I started to run into a blocking issue with the Extensions workshop.
0 kommentar(er)
