You are not logged in.
Been researching this heavily via these forums and reddit threads. I've attempted disabling ipv6 and lowering mtu, and I've even nuked my OS and done fresh installs. The wifi connection works on my mobile phone to lutris.net and legendary.gl, but on this system it appears to give the following with curl -L:
curl: (35) Recv failure: Connection reset by peerAnd ERR_CONNECTION_RESET on chromium based browsers and upon forced reload on Firefox browsers. When using a VPN these sites work fine but when using other devices connected to the same network they also work fine. I'm scratching my head wondering if it's something to do with this particular system and arch or just linux in general. Ethernet cables don't make a difference either so it can't be NIC. I'm honestly lost as to what to do here.
The following is the output of wget:
Prepended http:// to 'lutris.net'
--2024-12-16 03:52:45-- http://lutris.net/
Resolving lutris.net (lutris.net)... 104.21.16.1, 104.21.64.1, 104.21.48.1, ...
Connecting to lutris.net (lutris.net)|104.21.16.1|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://lutris.net/ [following]
--2024-12-16 03:52:46-- https://lutris.net/
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Connecting to lutris.net (lutris.net)|104.21.16.1|:443... connected.
GnuTLS: Error in the pull function.
Unable to establish SSL connection.It should be noted that this happens regardless of what DNS I use, either. I've used no DNS too.
dig lutris.net:
; <<>> DiG 9.20.4 <<>> lutris.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64206
;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;lutris.net. IN A
;; ANSWER SECTION:
lutris.net. 290 IN A 104.21.32.1
lutris.net. 290 IN A 104.21.16.1
lutris.net. 290 IN A 104.21.112.1
lutris.net. 290 IN A 104.21.48.1
lutris.net. 290 IN A 104.21.64.1
lutris.net. 290 IN A 104.21.96.1
lutris.net. 290 IN A 104.21.80.1
;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Mon Dec 16 03:56:23 PST 2024
;; MSG SIZE rcvd: 151Last edited by Lumenohr (2025-02-14 19:02:34)
Offline
curl -vL "http://blog.fefe.de/" > /dev/null
curl -vL "https://blog.fefe.de/" > /dev/nulland check your system time - you posted at 19:55 UTC but the dig says 03:56 PST which is like 7h late.
Offline
curl -vL "http://blog.fefe.de/" > /dev/null
curl -vL "https://blog.fefe.de/" > /dev/null:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Host blog.fefe.de:80 was resolved.
* IPv6: 2001:4d88:3508::fefe:b106
* IPv4: 31.15.64.162
* Trying [2001:4d88:3508::fefe:b106]:80...
* Immediate connect fail for 2001:4d88:3508::fefe:b106: Network is unreachable
* Trying 31.15.64.162:80...
* Connected to blog.fefe.de (31.15.64.162) port 80
* using HTTP/1.x
> GET / HTTP/1.1
> Host: blog.fefe.de
> User-Agent: curl/8.11.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 200 Here you go
< Server: Gatling/0.17
< Content-Type: text/html; charset=utf-8
< Content-Length: 22224
< Last-Modified: Sun, 15 Dec 2024 18:19:18 GMT
< Date: Sun, 15 Dec 2024 21:06:32 GMT
< X-Frame-Options: DENY
< Content-Security-Policy: frame-ancestors 'none';
<
{ [2531 bytes data]
100 22224 100 22224 0 0 17679 0 0:00:01 0:00:01 --:--:-- 17666
* Connection #0 to host blog.fefe.de left intact
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Host blog.fefe.de:443 was resolved.
* IPv6: 2001:4d88:3508::fefe:b106
* IPv4: 31.15.64.162
* Trying [2001:4d88:3508::fefe:b106]:443...
* Immediate connect fail for 2001:4d88:3508::fefe:b106: Network is unreachable
* Trying 31.15.64.162:443...
* ALPN: curl offers h2,http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: none
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):
{ [1 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [10 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [2988 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [520 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / x25519 / RSASSA-PSS
* ALPN: server did not agree on a protocol. Uses default.
* Server certificate:
* subject: CN=alternativlos.org
* start date: Nov 29 10:01:01 2024 GMT
* expire date: Feb 27 10:01:00 2025 GMT
* subjectAltName: host "blog.fefe.de" matched cert's "blog.fefe.de"
* issuer: C=US; O=Let's Encrypt; CN=R11
* SSL certificate verify ok.
* Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
* Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption
* Connected to blog.fefe.de (31.15.64.162) port 443
* using HTTP/1.x
} [5 bytes data]
> GET / HTTP/1.1
> Host: blog.fefe.de
> User-Agent: curl/8.11.1
> Accept: */*
>
* Request completely sent off
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [249 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [249 bytes data]
< HTTP/1.1 200 Here you go
< Server: Gatling/0.17
< Content-Type: text/html; charset=utf-8
< Content-Length: 22224
< Last-Modified: Sun, 15 Dec 2024 18:19:18 GMT
< Date: Sun, 15 Dec 2024 21:06:33 GMT
< X-Frame-Options: DENY
< Content-Security-Policy: frame-ancestors 'none';
< Strict-Transport-Security: max-age=1209600
<
{ [7927 bytes data]
100 22224 100 22224 0 0 16444 0 0:00:01 0:00:01 --:--:-- 16450
* Connection #0 to host blog.fefe.de left intact/etc/localtime shows Asia/Manila, as it should. Just did sudo hwclock --systohc
and check your system time - you posted at 19:55 UTC but the dig says 03:56 PST which is like 7h late.
Now sudo hwclock --show shows:
2024-12-16 05:11:33.861532+08:00Offline
Ah, that's *not* Pacific Standard Time ![]()
You also could access fefe via https, so that's not it ![]()
curl -vL "https://lutris.net/" > /dev/nullOffline
Ah, that's *not* Pacific Standard Time
You also could access fefe via https, so that's not it
Yeah haha. It didn't mean Pacific Standard Time. Also,
curl -vL "https://lutris.net/" > /dev/null:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Host lutris.net:443 was resolved.
* IPv6: 2606:4700:3030::6815:3001, 2606:4700:3030::6815:1001, 2606:4700:3030::6815:2001, 2606:4700:3030::6815:5001, 2606:4700:3030::6815:6001, 2606:4700:3030::6815:7001, 2606:4700:3030::6815:4001
* IPv4: 104.21.96.1, 104.21.48.1, 104.21.80.1, 104.21.32.1, 104.21.16.1, 104.21.112.1, 104.21.64.1
* Trying [2606:4700:3030::6815:3001]:443...
* Immediate connect fail for 2606:4700:3030::6815:3001: Network is unreachable
* Trying [2606:4700:3030::6815:1001]:443...
* Immediate connect fail for 2606:4700:3030::6815:1001: Network is unreachable
* Trying [2606:4700:3030::6815:2001]:443...
* Immediate connect fail for 2606:4700:3030::6815:2001: Network is unreachable
* Trying [2606:4700:3030::6815:5001]:443...
* Immediate connect fail for 2606:4700:3030::6815:5001: Network is unreachable
* Trying [2606:4700:3030::6815:6001]:443...
* Immediate connect fail for 2606:4700:3030::6815:6001: Network is unreachable
* Trying [2606:4700:3030::6815:7001]:443...
* Immediate connect fail for 2606:4700:3030::6815:7001: Network is unreachable
* Trying [2606:4700:3030::6815:4001]:443...
* Immediate connect fail for 2606:4700:3030::6815:4001: Network is unreachable
* Trying 104.21.96.1:443...
* ALPN: curl offers h2,http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: none
* Recv failure: Connection reset by peer
* TLS connect error: error:00000000:lib(0)::reason(0)
* OpenSSL SSL_connect: Connection reset by peer in connection to lutris.net:443
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
* closing connection #0
curl: (35) Recv failure: Connection reset by peerLast edited by Lumenohr (2024-12-15 21:39:47)
Offline
What does
ip asay?
Offline
What does
ip asay?
ip a:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: enp14s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether d8:43:ae:60:ea:65 brd ff:ff:ff:ff:ff:ff
altname enxd843ae60ea65
3: wlp18s0f3u2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 9c:a2:f4:cc:19:00 brd ff:ff:ff:ff:ff:ff
altname wlx9ca2f4cc1900
inet 192.168.254.194/24 brd 192.168.254.255 scope global dynamic noprefixroute wlp18s0f3u2
valid_lft 251212sec preferred_lft 251212sec
inet6 fe80::7647:95b:9e76:2641/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: wlp15s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 86:7e:18:9c:ea:60 brd ff:ff:ff:ff:ff:ff permaddr fc:b0:de:74:6a:ed
altname wlxfcb0de746aedOffline
Not sure why you're going for IPv6 first when you only have a LLA, but are all the failing pages hosted by cloudflare?
And maybe globally disable IPv6 to completely get that out of the way: https://wiki.archlinux.org/title/IPv6#D … ctionality
Offline
Not sure why you're going for IPv6 first when you only have a LLA, but are all the failing pages hosted by cloudflare?
I don't believe so. I've visited other cloudflare pages I believe.
And maybe globally disable IPv6 to completely get that out of the way: https://wiki.archlinux.org/title/IPv6#D … ctionality
I just tried that. Sadly, it didn't work.
cat /etc/sysctl.d/40-ipv6.conf
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.wlp18s0f3u2.disable_ipv6 = 1Last edited by Lumenohr (2024-12-15 22:06:47)
Offline
I'd go w/ the "ipv6.disable=1" kernel parameter.
Instead of believing around: can you provide more samples of inaccessible webpages?
Offline
I'd go w/ the "ipv6.disable=1" kernel parameter.
Just did that too. Unfortunately no fish. In Firefox browsers im getting the following now:
Secure Connection Failed
An error occurred during a connection to hyprland.org. PR_CONNECT_RESET_ERROR
Error code: PR_CONNECT_RESET_ERROR
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.Instead of believing around: can you provide more samples of inaccessible webpages?
Well, so far, there are:
hyprland.org
wiki.hyprland.org
lutris.net
legendary.gl
and some others.
But I can ping the websites. Still getting the same kind of outputs with curl though:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Host lutris.net:443 was resolved.
* IPv6: (none)
* IPv4: 104.21.48.1, 104.21.64.1, 104.21.112.1, 104.21.80.1, 104.21.16.1, 104.21.96.1, 104.21.32.1
* Trying 104.21.48.1:443...
* ALPN: curl offers h2,http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: none
* Recv failure: Connection reset by peer
* TLS connect error: error:00000000:lib(0)::reason(0)
* OpenSSL SSL_connect: Connection reset by peer in connection to lutris.net:443
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
* closing connection #0
curl: (35) Recv failure: Connection reset by peerdig lutris.net:
; <<>> DiG 9.20.4 <<>> lutris.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58651
;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;lutris.net. IN A
;; ANSWER SECTION:
lutris.net. 143 IN A 104.21.112.1
lutris.net. 143 IN A 104.21.64.1
lutris.net. 143 IN A 104.21.80.1
lutris.net. 143 IN A 104.21.16.1
lutris.net. 143 IN A 104.21.32.1
lutris.net. 143 IN A 104.21.96.1
lutris.net. 143 IN A 104.21.48.1
;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Mon Dec 16 06:44:41 PST 2024
;; MSG SIZE rcvd: 151Last edited by Lumenohr (2024-12-15 22:48:42)
Offline
Those are all hosted on cloudflare…
* wifi connection works on my mobile phone
* using a VPN these sites work fine
* other devices connected to the same network they also work fine
What are those "other devices"? Can you access those domains from the concerned host when booting some life distro like https://grml.org ?
Offline
Those are all hosted on cloudflare…
* wifi connection works on my mobile phone
* using a VPN these sites work fine
* other devices connected to the same network they also work fineWhat are those "other devices"? Can you access those domains from the concerned host when booting some life distro like https://grml.org ?
Tested on my other devices and it seems that they don't work, save for my phone. Now, what's interesting about my phone is that it used CLOUDFLARE DNS, which is probably why it's able to access the sites! Now, I've been trying to set up cloudflare DNS on my end, but it doesn't seem to allow me to connect to the sites like it does with my phone. Is it because my phone uses some other way to configure Cloudflare's DNS servers?
Offline
Note: I've tried a lot of things. I've tried different DNS resolvers like dnsmasq and dnscrypt-proxy and even stubby, but I can't seem to get it to work like my phone. My phone somehow has it configured correctly with Cloudflare's DNS servers. Currently trying to use systemd-resolved with dnscrypt-proxy.
Edit: Sorry for the late reply, by the way.
Last edited by Lumenohr (2024-12-16 00:38:45)
Offline
Getting the following with cloudflared now:
FTL Failed to open the metrics listener error="listen tcp: lookup localhost: no such host"Edit: Had to comment out the following in /etc/hosts:
::1 localhostLast edited by Lumenohr (2024-12-16 00:52:40)
Offline
I think I'm close to cracking it and need to figure out what's wrong with my DNS config. The following is the only head scratcher when testing out cloudflare's DNS:
dig +short @127.0.0.1 cloudflare.com yields:
;; communications error to 127.0.0.1#53: connection refused
;; communications error to 127.0.0.1#53: connection refused
;; communications error to 127.0.0.1#53: connection refused
;; no servers could be reachedMy /etc/hosts is the following:
# Static table lookup for hostnames.
# See hosts(5) for details.
127.0.0.1 localhost
#:: localhost
127.0.1.1 arch.mylocaldomain archand ss -tulpen | grep 53 yields:
udp UNCONN 0 0 127.0.0.1:5300 0.0.0.0:* uid:62260 ino:56124 sk:1001 cgroup:/system.slice/cloudflared.service <->
udp UNCONN 0 0 0.0.0.0:5353 0.0.0.0:* uid:976 ino:63721 sk:1002 cgroup:/system.slice/systemd-resolved.service <->
udp UNCONN 0 0 0.0.0.0:5355 0.0.0.0:* uid:976 ino:63718 sk:1003 cgroup:/system.slice/systemd-resolved.service <->
udp UNCONN 0 0 127.0.0.54:53 0.0.0.0:* uid:976 ino:63728 sk:1004 cgroup:/system.slice/systemd-resolved.service <->
udp UNCONN 0 0 127.0.0.53%lo:53 0.0.0.0:* uid:976 ino:63726 sk:1005 cgroup:/system.slice/systemd-resolved.service <->
tcp LISTEN 0 4096 0.0.0.0:5355 0.0.0.0:* uid:976 ino:63719 sk:1006 cgroup:/system.slice/systemd-resolved.service <->
tcp LISTEN 0 4096 127.0.0.1:5300 0.0.0.0:* uid:62260 ino:56126 sk:1007 cgroup:/system.slice/cloudflared.service <->
tcp LISTEN 0 4096 127.0.0.54:53 0.0.0.0:* uid:976 ino:63729 sk:1008 cgroup:/system.slice/systemd-resolved.service <->
tcp LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:* uid:976 ino:63727 sk:1009 cgroup:/system.slice/systemd-resolved.service <->And /etc/resolv.conf is linked via sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf and yields:
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0 trust-ad
search .Last edited by Lumenohr (2024-12-16 01:14:22)
Offline
Okay, so I've figured out the dig command is only relevant when using it on 127.0.0.53, and it seems that that outputs it just fine. However, I'm still unable to connect for some reason? This is a real head scratcher since Cloudflare dns SHOULD make this work. Is it the port cloudflared is running on? The following is my current systemd service file for it:
[Unit]
Description=DNS over HTTPS proxy client
Wants=network-online.target nss-lookup.target
Before=nss-lookup.target
[Service]
AmbientCapabilities=CAP_NET_BIND_SERVICE
CapabilityBoundingSet=CAP_NET_BIND_SERVICE
DynamicUser=yes
ExecStart=/usr/bin/cloudflared proxy-dns --address 127.0.0.53 --port 5300
[Install]
WantedBy=multi-user.targetLast edited by Lumenohr (2024-12-16 01:28:27)
Offline
Okay it's solved. I ended up using the cloudflare warp client via cloudflare-warp-bin.
Edit: Nevermind. My internet is slower with cloudflare warp. Any other solutions?
Last edited by Lumenohr (2024-12-16 01:56:39)
Offline
Just looked into warp and realized it was a VPN. How do I actually fix my network with Cloudflare DNS?
Offline
I personally think your chasing phantoms here (Cloudflare DNS) - your posts from above indicate that your DNS setup is O.K.
The phenomena sound like a MTU problem - which is exceedingly rare under non-VPN connections. Try lower your WiFi MTU value.
Offline
I personally think your chasing phantoms here (Cloudflare DNS) - your posts from above indicate that your DNS setup is O.K.
The phenomena sound like a MTU problem - which is exceedingly rare under non-VPN connections. Try lower your WiFi MTU value.
I've done so. It's now 1420 but the result is the same unfortunately.
Edit: Just tried 1300 to no avail.
Last edited by Lumenohr (2024-12-16 06:59:14)
Offline
O.K. - that's not the cause either.
Sounds to me like a more hardware-based communication problem specific to your WiFi adapter hardware in conjunction with your router.
Additionally: If I set up an Arch VM with only IPv4 available curl does not try the IPv6 address first! I can't think of a configuration in which your system does that. That is probably pointing to the real cause.
Last edited by -thc (2024-12-16 07:34:00)
Offline
O.K. - that's not the cause either.
Sounds to me like a more hardware-based communication problem specific to your WiFi adapter hardware in conjunction with your router.
Additionally: If I set up an Arch VM with only IPv4 available curl does not try the IPv6 address first! I can't think of a configuration in which your system does that.
I genuinely think it's just my internet at this point. Other devices, besides the phone with Cloudflare dns, don't work on the same websites.
Offline
DNS is fine, you don't have any problems to resolve valid IPs in your previous curls.
Is your phone in the same subnet or even using the same ISP as the rest of the network?
Does it work if you use it via wifi on the affected subnet?
Have you tried to restart your modem-router-switch to get a new IP from your ISP?
(You, resp. your WAN IP might just be banned for abuse)
On a formal note: please don't bump and please don't blog.
Edit your previous posts to mend them if nobody has yet replied.
Offline
DNS is fine, you don't have any problems to resolve valid IPs in your previous curls.
Is your phone in the same subnet or even using the same ISP as the rest of the network?
Yes it's connected to the same wifi network. I don't see why the ISP would change.
Does it work if you use it via wifi on the affected subnet?
I'm not sure I completely understand how to do that, but I'm just seeing that my phone is connected to the same WLAN as my other devices.
Have you tried to restart your modem-router-switch to get a new IP from your ISP?
(You, resp. your WAN IP might just be banned for abuse)
I have. I turned it off for ten seconds then turned it on again. Same thing.
On a formal note: please don't bump and please don't blog.
Edit your previous posts to mend them if nobody has yet replied.
My bad. Sorry I was kind of just going through the motions. I can just delete them since most of them are, as @-thc aptly put it, just me chasing phantoms.
Edit: Uhh can you even delete posts on this forum? It's not showing me an option to. If it's all right, can any of the admins delete them?
Edit 2: Seems like it fixed itself. Oh well.
Last edited by Lumenohr (2025-02-14 19:01:21)
Offline