Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR after installing CertBot on my ubuntu vps with nginx

Help
1

sadfasdnlew jkf wenjkf newjk fnejk fnejk fnejk e how do i delete

2

Welcome to the community @evizzo

I connect to your site just fine. And, SSL Labs reports a "A" score: SSL Server Test: gdedaizadjemna.ovh (Powered by Qualys SSL Labs)

Can you describe more about the device or URL you are using that gets this error?

Your nginx looks fine to me too.

3 Likes
3

Thanks for welcoming me !

It seems now that my frontend wont communicate with backend or oauth2 with google, i did set up CORS and everything, but it seems whenever my fronted now tries to talk to backend i get error for example

"GET https://www.gdedaizadjemna.ovh:8080/spot/search?name=&city=&workingFrom=&workingTo=&alwaysOpen=false&outdoorSeating=false&wifiAvailable=false&parking=false&petsAllowed=false&hasSpecialDietaryOptionVegetarian=false&hasSpecialDietaryOptionVegan=false&hasSpecialDietaryOptionGlutenFree=false&hasFitnessMenu=false&hasPosnaFood=false&hasBreakfast=false&spotType=&childsPlayground=false net::ERR_SSL_PROTOCOL_ERROR"

Im using a ubuntu laptop with brave browser to access the site, i tried running it in incognito too.

It all worked until i added certbot and switched to https

1 Like
4

You are using HTTPS to connect to your domain on port 8080. But, your port 8080 is configured only for HTTP. That is specifically why it fails.

But, why do you specify port 8080 in that URL? You have nginx setup to proxy to your backend servers on ports 8080 and 8081 (using HTTP as seems reasonable). Can't you just use that same URL but without ":8080" in it?

Further, usually those backend ports are blocked so requests from the public internet cannot reach them. You usually want people to connect to your frontend nginx and use it to proxy to your own backend servers.

4 Likes
5

I tried using port 443 or using no port but i get CORS error and 404 not found error

6

CORS and 404 errors are application design problems. Not directly related to the cert which is just allowing you to use HTTPS

Perhaps review this Mozilla guide on CORS.

2 Likes
7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.