Feedback Technical Grievances

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
I was trying to upload a .jpg image and this message came up:

Screenshot_20240714_145937.jpg

Why would this happen to that specific image?
 
  • Like
Reactions: Neo-Nazi Rich Evans and UnsufficentBoobage
I've been having on and off issues with connecting to the site via Brave on mobile. I'm using mobile data, but I'm able to access it through TOR.
 
When editing a post, the thread's ID is for some reason included in the box. Leftover from something being debugged?
1720988981057.png
 
  • Like
Reactions: Meiwaku
/styles/custom/emotes/salt.gif
/styles/custom/emotes/nitenite.webp
/styles/custom/emotes/ramona.webp?4

Does anyone have these three old emotes?
 

Attachments

  • ramona-ralph.png
    ramona-ralph.png
    11.2 KB · Views: 941
  • nitenite.gif
    nitenite.gif
    21.6 KB · Views: 875
  • felted.gif
    felted.gif
    2.9 KB · Views: 1,271
Connecting via AT&T cellular.

Chrome, edge, and brave return Forbidden certificate error. Process denied for www.kiwifarms.net and www.kiwifarms.st.

Samsung Opera, Google Chrome and brave mobile via AT&T return Forbidden certificate error. Process denied for www.kiwifarms.net and www.kiwifarms.st

Chrome, Edge and Brave return "no data received error" for https://kiwifarms.net and https://kiwifarms.st.

Samsung Opera, Google Chrome, and Brave Mobile return "no data received error" for https://kiwifarms.net and https://kiwifarms.st.

TOR browser Brave connected via Onion circuit to www.kiwifarms.net redirects with no issue. Https://kiwifarms.net via Brave onion circuit connects no issue.

TOR Mobile Browser connects to www.kiwifarms.net via redirect no issue. Connects to https://kiwifarms.st no issue.

All connections done in the clear via AT&T mobile network.

AT&T in the clear connection is being blocked, and requiring a redirect to get around the block.

I can no longer connect to the website via clearnet confirmed.
 
mindlessobserver said:
Connecting via AT&T cellular.

Chrome, edge, and brave return Forbidden certificate error. Process denied for www.kiwifarms.net and www.kiwifarms.st.

Samsung Opera, Google Chrome and brave mobile via AT&T return Forbidden certificate error. Process denied for www.kiwifarms.net and www.kiwifarms.st
Click to expand...
Stop trying www.kiwifarms.anything it's not going to work.

The site is otherwise having glitches, maybe DDOS, maybe Null spilled his Monster(tm) on the server again.
 
  • Like
Reactions: grapeshark77
davids877 said:
Stop trying www.kiwifarms.anything it's not going to work.

The site is otherwise having glitches, maybe DDOS, maybe Null spilled his Monster(tm) on the server again.
Click to expand...
The https:// addresses don't work either.

If I use the www. Addresses I get an honest answer. Fuck you. If I use the https: addresses the system ponders and then says oopsie, something went fucky wucky, idgaf >_<
 
I need to stress my ONLY connection to the internet is in the clear mobile AT&T cellular. For both PC and Mobile. There is no satellite. There is no WiFi. There is no cable. There is no Fiber Optic. There is only that cell phone tower a mile from my house.
 
And suddenly everything is working fine on both mobile and computer. Even the www. Addresses.

I want to say disregard but I am feeling like I am going crazy. Maybe Null put a fix in today that has finally caught up? Literally as I am bitching about it?

Everything works fine now.
 
Null said:
Certificates are valid. Can anyone replicate the issue?
Click to expand...
www?
It appears SNI is in use and it's not aware www.kiwifarms.net is valid so it's using one of those fancy self-signed and expired certs.

Code: 
$ openssl s_client -showcerts -servername www.kiwifarms.net -connect www.kiwifarms.net:443
CONNECTED(00000003)
depth=0 C = AU, ST = Some-State, O = Internet Widgits Pty Ltd
verify error:num=18:self-signed certificate
verify return:1
depth=0 C = AU, ST = Some-State, O = Internet Widgits Pty Ltd
verify error:num=10:certificate has expired
notAfter=Nov 28 00:42:58 2023 GMT
verify return:1
depth=0 C = AU, ST = Some-State, O = Internet Widgits Pty Ltd
notAfter=Nov 28 00:42:58 2023 GMT
verify return:1
---
Certificate chain
 0 s:C = AU, ST = Some-State, O = Internet Widgits Pty Ltd
   i:C = AU, ST = Some-State, O = Internet Widgits Pty Ltd
   a:PKEY: rsaEncryption, 4096 (bit); sigalg: RSA-SHA256
   v:NotBefore: Oct 29 00:42:58 2023 GMT; NotAfter: Nov 28 00:42:58 2023 GMT
-----BEGIN CERTIFICATE-----
omitted
-----END CERTIFICATE-----
---
Server certificate
subject=C = AU, ST = Some-State, O = Internet Widgits Pty Ltd
issuer=C = AU, ST = Some-State, O = Internet Widgits Pty Ltd
---
No client certificate CA names sent
Peer signing digest: SHA256
Peer signature type: RSA-PSS
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 2207 bytes and written 403 bytes
Verification error: certificate has expired
---
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 4096 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 10 (certificate has expired)
---
---
Post-Handshake New Session Ticket arrived:
SSL-Session:
    Protocol  : TLSv1.3
    Cipher    : TLS_AES_256_GCM_SHA384
    Session-ID: 088F406D3BFB5D27546E22AA395C5DDC0DBFA15C80C40E8B7204BAD43B24A204
    Session-ID-ctx:
    Resumption PSK: 957AA6A709739206D58C9F8535BDEE51DEA4ADA396EA1ECBC856BB0CA0967A43FDA06910D1303DE9B1D4B7A9CD825EAC
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 86400 (seconds)
    TLS session ticket:
    0000 - 87 a9 51 e9 e9 f2 1b ab-27 fc 8e a2 33 aa b8 b6   ..Q.....'...3...
    0010 - 05 23 13 3b c9 2a d1 07-37 e3 a3 d0 58 c5 5f 99   .#.;.*..7...X._.

    Start Time: 1721277652
    Timeout   : 7200 (sec)
    Verify return code: 10 (certificate has expired)
    Extended master secret: no
    Max Early Data: 0
---
read R BLOCK
---
Post-Handshake New Session Ticket arrived:
SSL-Session:
    Protocol  : TLSv1.3
    Cipher    : TLS_AES_256_GCM_SHA384
    Session-ID: 5E6518C22148D6E17B60B4E83C3E1FFF10152B38E6E5ABC297ECAD2174F5AB26
    Session-ID-ctx:
    Resumption PSK: 275B623EC8256A10C97CF1515BE8A6C2CEB0CEBC5961F52085EF2CF92713A3A60C4BBDB9B3354B10D7B55C1CB536B3A7
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    TLS session ticket lifetime hint: 86400 (seconds)
    TLS session ticket:
    0000 - ea 9d 70 4f 31 0a f1 85-cd 0f d0 db 4c 60 9b f3   ..pO1.......L`..
    0010 - 1b 0a fa 88 b1 41 db 8b-9f a2 01 dc 78 e8 b5 f3   .....A......x...

    Start Time: 1721277652
    Timeout   : 7200 (sec)
    Verify return code: 10 (certificate has expired)
    Extended master secret: no
    Max Early Data: 0
---
read R BLOCK
40C71528427F0000:error:0A000126:SSL routines:ssl3_read_n:unexpected eof while reading:../ssl/record/rec_layer_s3.c:303:

www.kiwifarms.st does the same.
 
  • Agree
Reactions: Billy Bong
Ogre Magi said:
Also, is Sneedchat down for anyone else? I haven't been able to connect for hours now.
Click to expand...
It's working ok for me now but was TTDing to the max earlier. Some people are complaining and my bot was struggling with timeouts. I think the problem IP is 212.23.222.98 as it's responding on :443 but not the Sneedchat port :9443. All the other IPs seem fine except that one.

If you're using Firefox try going to about:networking#dns and clear the DNS cache. If you're on a Chrome-clone then you can find the equivalent under chrome://net-internals/#dns

Hopefully after wiping the cache and retrying it'll fixate on a working IP address.
 
  • Informative
Reactions: Billy Bong and Ogre Magi
You must log in or register to reply here.
Back