Ask coding questions

← Back to all posts
Site going insecure
h
Baconman321

I am collaborating with a fellow repler (tussiez), and he and I are experiencing a problem where the site goes insecure. If you click the little "i" icon to the left of the address (chrome), it says the site is not secure and doesn't show a certificate. However, in dev tools it says certificate is valid and trusted, but doesn't allow you to view the certificate. It also says "This origin is a non-HTTPS secure origin." This is the same message I get in localhost, so I don't get what is happening (since I am going to the https URL of the site).

I think this may have to do with service workers, as my other site I made myself has this problem too, and it runs a service worker (as well as the site I am collaborating on with tussiez). Could this be a repl.it problem, or is it just something with service workers? I really would appreciate the help.

Answered by Coder100 [earned 5 cycles]
View Answer
Voters
mranonymous481
Baconman321
Comments
hotnewtop
Coder100

well, what's the URL?

I doubt service workers and any of that actually change anything, but for the most part, HTTPs should be working.

Baconman321

@Coder100 https://sortacraft-1.tussiez.repl.co I think it might just be that I was serving main files from cache, but IDK. Works better now that I stopped serving main files from cache.

Coder100

@Baconman321

pretty secure if I say so myself

one thing you should try is to make all urls relative, so to not prevent automatic http assignment

Baconman321

@Coder100 Yeah, IDK why that was happening. Otherwise, eh.

Coder100

eh http is no big deal, as long as you don't use any sockets, it should be very boring to hack (if you can at all) @Baconman321

Baconman321

@Coder100 It's more that it requires https for PWA and service workers

RYANTADIPARTHI

then you need to add a https to the front of it. when it's lacking.

Baconman321

@RYANTADIPARTHI As I told programmeruser, there is https in the url, it's not showing security tho. Like I said, it may just be that I'm serving some of the main pages from cache. I don't know...