Feedback Technical Grievances

Reporting that since the introduction of the Kiwiflare, images (including embed ss and profile pics) are very slow to load or mostly don’t load at all. Also can only sticker ’like’ on mobile. ‘Like’ registers as the ‘copy.paste.etc’ bar on touch and hold instead of sticker choice.
 
Also getting the white screen on Brave and on mobile. I can access a few pages like the subforums and managed to get linked to this thread through chat. Front page and most threads are just pure white. Checking the html source and it's empty.
 
Null said:
Both work for me. Are supplying a session cookie or any headers? What TLS version do you see in the output?
Click to expand...
No cookies, just a quick test with curl, the website is also now working if I disable http/2 in my browser. I'm using librewolf a firefox fork.
It says 1.3, here is the full output:
Code: 
*   Trying 103.114.191.1:443...
* Connected to kiwifarms.net (103.114.191.1) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS handshake, Client hello (1):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Server hello (2):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Certificate (11):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, CERT verify (15):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Finished (20):
* [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=*.kiwifarms.net
*  start date: Dec 25 00:00:00 2022 GMT
*  expire date: Dec 25 23:59:59 2023 GMT
*  subjectAltName: host "kiwifarms.net" matched cert's "kiwifarms.net"
*  issuer: C=LV; L=Riga; O=GoGetSSL; CN=GoGetSSL RSA DV CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* h2h3 [:method: GET]
* h2h3 [:path: /]
* h2h3 [:scheme: https]
* h2h3 [:authority: kiwifarms.net]
* h2h3 [user-agent: curl/7.87.0]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x5593fef89fd0)
> GET / HTTP/2
> Host: kiwifarms.net
> user-agent: curl/7.87.0
> accept: */*
>
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
< HTTP/2 200
< server: openresty
< date: Fri, 03 Feb 2023 11:24:53 GMT
< content-type: text/html; charset=utf-8
< content-length: 0
< x-frame-options: SAMEORIGIN
< x-content-type-options: nosniff
< last-modified: Fri, 03 Feb 2023 11:24:52 GMT
< expires: Thu, 19 Nov 1981 08:52:00 GMT
< cache-control: private, no-cache, max-age=0
< set-cookie: xf_dbWriteForced=1675423493; path=/; secure; HttpOnly
< x-sneed: CHUCK
<
* Connection #0 to host kiwifarms.net left intact

Code: 
* Connected to kiwifarms.net (103.114.191.1) port 443 (#0)
* ALPN: offers http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
} [5 bytes data]
* [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [25 bytes data]
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [4503 bytes data]
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* [CONN-0-0][CF-SSL] TLSv1.3 (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.kiwifarms.net
*  start date: Dec 25 00:00:00 2022 GMT
*  expire date: Dec 25 23:59:59 2023 GMT
*  subjectAltName: host "kiwifarms.net" matched cert's "kiwifarms.net"
*  issuer: C=LV; L=Riga; O=GoGetSSL; CN=GoGetSSL RSA DV CA
*  SSL certificate verify ok.
} [5 bytes data]
> GET / HTTP/1.1
> Host: kiwifarms.net
> User-Agent: curl/7.87.0
> Accept: */*
>
{ [5 bytes data]
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [265 bytes data]
* [CONN-0-0][CF-SSL] TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [265 bytes data]
* old SSL session ID is stale, removing
{ [5 bytes data]
* Mark bundle as not supporting multiuse
< HTTP/1.1 200
< server: openresty
< date: Fri, 03 Feb 2023 11:20:55 GMT
< content-type: text/html; charset=utf-8
< vary: Accept-Encoding
< x-frame-options: SAMEORIGIN
< x-content-type-options: nosniff
< expires: Fri, 03 Feb 2023 11:20:59 GMT
< cache-control: private, no-cache, max-age=0
< x-xf-cache-status: HIT
< set-cookie: xf_csrf=38MQ_nF47AfdmbEA; path=/; secure
< x-sneed: CHUCK
< transfer-encoding: chunked

edit: formatting,
 
Last edited:
Looks like I am still getting the blank page CHUCK response if I try to view the alert page in the upper right side of the page with http/1.1 in my browser. The rest of the site sometimes give me a blank page too,
 
There's an issue with the backend and I don't know what causes it. I don't believe it's related to http method. There is probably something deeper.
 
Whatever you did, its somehow working for now, thanks much, I can sneed comfily again.
Sneeding over http/2 fine now.
 
Ok, I encountered the error myself and was able to do some diagnostics. I've applied something I think may fix it. Let me know if you encounter the error on clearnet.
 
Null said:
Ok, I encountered the error myself and was able to do some diagnostics. I've applied something I think may fix it. Let me know if you encounter the error on clearnet.
Click to expand...
Clearnet still error within less than 1 min after login, says the "address cannot be found", regardless the VPN. TOR seems still viable. What's happening?
 
You must log in or register to reply here.
Back