/meta/ - 16chan Discussion

Discussion, Feedback, and Improvement of 16chan

Posting Mode: Reply Return

Max message length: 5000


(used to delete files and postings)


  • Supported file types: GIF, JPG, PNG, WebM, OGG, and more
  • Max files: 5
  • Max file size: 50.00 MB
  • Read the global rules before you post, as well as the board rules found in the sticky.

08/28/20 Come and join our Matrix/IRC servers, the info can be found here.
02/09/20 /ausneets/ has been added!
11/23/19 Donations can now be made via PayPal, thank you for all of your support!
11/21/19 We have successfully migrated to LynxChan 2.3.0, to see all of the changes to 16chan, click here.

[Index] [Catalog] [Archive] [Bottom] [Refresh]

HTTPS error Anonymous 09/18/2019 (Wed) 03:01:11 No. 125
When I try to access this site through either firefox or Tor Browser I get this error. I can access it through chromium with no issue though.
Doesn't work for icecat 52.3, firefox 66 and firefox 69.
Weird issue, I haven't had any other reports of this thus far. Tor browser should work just fine, and so should any version of Firefox. I will investigate this if more reports come up.

Can you try those browsers on a different device by chance, and see if it persists, or perhaps another connection?
clear cache
(96.93 KB 997x1049 kinda-homo-tbh.png)

I'm a different user. Getting this error for the first time today on tor browser, worked fine yesterday.

not willing to connect from anything other than tor, sorry can't test more
Just tested on like 3-4 different devices and SSL works fine for me.
(34.31 KB 987x587 type-16chan-get-this-screen.png)
(13.32 KB 699x447 latest-tor-browser.png)
irrelevant. tor doesn't have a cache

SSL works for me too, once I confirm the exception. I'm using it now to post. The issue is the initial untrusted nature of the certificate. I've attached the initial splash screen I currently get for https://www.16chan.xyz

Some DDG'ing suggests you may need to manually append some intermediate certificates so you get the full trust path, but I'm no expert

I've closed and relaunched tor a few times and have consistently got this error every time today in the last ~30 minutes. Perhaps later I'll try with some different devices (also running latest tor browser on linux), if the problem persists.
I'm not using a LetsEncrypt certificate, I'm using a Comodo one. I'll switch to LetsEncrypt tomorrow night.
>>125 I'v had no issue with firefox

Same here, tried Tor here for the first time cache is zero get same warning, Tor is fresh install 8.5.5 (based on Mozilla Firefox 60.9.0esr) (64-bit)

Your connection is not secure

The owner of 16chan.xyz has configured their website improperly. To protect your information from being stolen, Tor Browser has not connected to this website.

Learn more…

16chan.xyz uses an invalid security certificate.

The certificate is not trusted because the issuer certificate is unknown.
The server might not be sending the appropriate intermediate certificates.
An additional root certificate may need to be imported.

Sorry should not have said
>same here
as it implies "works fine for me"

With FF I have no issue but TOR is returning an error
Issue will be fixed tomorrow, I'll switch to new certificates. I'm out of town tonight.
So the site was just working with icecat (still wasn't working with tor) but for some I started getting the same error as I was about to post an update.
I thought that maybe it takes time for the certificates a browser trusts to update, but honestly I have no idea how this shit works.
(115.58 KB 640x480 comptr.jpeg)
I think >344 was intended for this thread.
I'm now getting Error code: SSL_ERROR_BAD_CERT_DOMAIN on both Tor and Firefox. Since you just swapped certs, I wouldn't worry too much about it unless others also report the same thing. If I've still got the issue after 24 hours + update + reboot cycle I'll post back here.
Thanks for all the stuff you do, big BOss.
Thanks! Appreciate it.
(1.12 MB 480x339 mfw-cert-error.gif)
Figured it out.
"https://16chan.xyz" = good
"https://www.16chan.xyz" = cert error
Ill get that fixed. Thank you.
305, 310 poster here, working for me too now,
www not, but who the hell uses www anymore? kek

Also never knew there was a difference, learn something new everyday.
Just tried with firefox sure enough www returned error.

The network administrator for the domain "howstuffworks.com" is in charge of mapping the names in the howstuffworks.com domain to specific machines and their IP addresses. In many large companies, there will be different machines (with different IP addresses) handling WWW, FTP, Telnet and other traffic. On smaller sites, the same machine can handle everything.

The network administrator makes a list of names and IP addresses, like this:

www.howstuffworks.com -
ftp.howstuffworks.com -

The­ administrator can put anything in that list, because the name servers don't care. The administrator could put in scooby.howstuffworks.com, scooby.doo.howstuffworks.com and scooby.dooby.doo.howstuffworks.com, and when someone types in those names the name server will return the IP addresses associated with them.

In the case of Web sites that happen to work without the "www" prefix, it simply means that the administrator has decided that if there is no prefix, the IP address returned should be the IP address for the Web server.
thanks again, for all your work BOss
how does it feels to have boomers on your board? topkek
exhibit A >>347


no cookies?