Skip to content

Conversation

@YuevUwU
Copy link
Contributor

@YuevUwU YuevUwU commented Feb 8, 2026

Preview the changes [here]

Issue

The old https://files-cf.phira.cn/github-showcase.png returns error code 521: Web server is down,
which has migrated to https://phira.5wyxi.com/files/github-showcase.png

Changes

NOTICE

Unstable GitHub Camo

Maybe some header, auth, redirect, or other limitation
It's UNSTABLE whether or not you successfully add as GitHub Camo.

cURL Log
alan54692@MSI:~/phira$ curl -v https://phira.5wyxi.com/files/github-showcase.png
* Host phira.5wyxi.com:443 was resolved.
* IPv6: (none)
* IPv4: 101.35.254.112
*   Trying 101.35.254.112:443...
* Connected to phira.5wyxi.com (101.35.254.112) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519 / RSASSA-PSS
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.5wyxi.com
*  start date: Jul 11 00:00:00 2025 GMT
*  expire date: Jul 31 23:59:59 2026 GMT
*  subjectAltName: host "phira.5wyxi.com" matched cert's "*.5wyxi.com"
*  issuer: C=CN; O=WoTrus CA Limited; CN=WoTrus DV Server CA  [Run by the Issuer]
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha384WithRSAEncryption
*   Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption
* using HTTP/1.x
> GET /files/github-showcase.png HTTP/1.1
> Host: phira.5wyxi.com
> User-Agent: curl/8.5.0
> Accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
< HTTP/1.1 303 See Other
< Server: nginx
< Date: Sun, 08 Feb 2026 17:41:14 GMT
< Content-Length: 0
< Connection: keep-alive
< location: https://phira-cdn.5wyxi.com/github-showcase.png?sign=ac4f5febc097d324d4b4862b60c11399&t=1770572474
< vary: origin, access-control-request-method, access-control-request-headers
< access-control-allow-origin: *
<
* Connection #0 to host phira.5wyxi.com left intact
alan54692@MSI:~/phira$ curl -Lv https://phira.5wyxi.com/files/github-showcase.png
* Host phira.5wyxi.com:443 was resolved.
* IPv6: (none)
* IPv4: 101.35.254.112
*   Trying 101.35.254.112:443...
* Connected to phira.5wyxi.com (101.35.254.112) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519 / RSASSA-PSS
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.5wyxi.com
*  start date: Jul 11 00:00:00 2025 GMT
*  expire date: Jul 31 23:59:59 2026 GMT
*  subjectAltName: host "phira.5wyxi.com" matched cert's "*.5wyxi.com"
*  issuer: C=CN; O=WoTrus CA Limited; CN=WoTrus DV Server CA  [Run by the Issuer]
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha384WithRSAEncryption
*   Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption
* using HTTP/1.x
> GET /files/github-showcase.png HTTP/1.1
> Host: phira.5wyxi.com
> User-Agent: curl/8.5.0
> Accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
< HTTP/1.1 303 See Other
< Server: nginx
< Date: Sun, 08 Feb 2026 17:41:22 GMT
< Content-Length: 0
< Connection: keep-alive
< location: https://phira-cdn.5wyxi.com/github-showcase.png?sign=4c21c5927c091dcc4cefa20f06913ea2&t=1770572482
< vary: origin, access-control-request-method, access-control-request-headers
< access-control-allow-origin: *
<
* Connection #0 to host phira.5wyxi.com left intact
* Issue another request to this URL: 'https://phira-cdn.5wyxi.com/github-showcase.png?sign=4c21c5927c091dcc4cefa20f06913ea2&t=1770572482'
* Host phira-cdn.5wyxi.com:443 was resolved.
* IPv6: (none)
* IPv4: 128.1.102.21
*   Trying 128.1.102.21:443...
* Connected to phira-cdn.5wyxi.com (128.1.102.21) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256 / X25519 / RSASSA-PSS
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=*.5wyxi.com
*  start date: Jul 11 00:00:00 2025 GMT
*  expire date: Jul 31 23:59:59 2026 GMT
*  subjectAltName: host "phira-cdn.5wyxi.com" matched cert's "*.5wyxi.com"
*  issuer: C=CN; O=WoTrus CA Limited; CN=WoTrus DV Server CA  [Run by the Issuer]
*  SSL certificate verify ok.
*   Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
*   Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha384WithRSAEncryption
*   Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://phira-cdn.5wyxi.com/github-showcase.png?sign=4c21c5927c091dcc4cefa20f06913ea2&t=1770572482
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: phira-cdn.5wyxi.com]
* [HTTP/2] [1] [:path: /github-showcase.png?sign=4c21c5927c091dcc4cefa20f06913ea2&t=1770572482]
* [HTTP/2] [1] [user-agent: curl/8.5.0]
* [HTTP/2] [1] [accept: */*]
> GET /github-showcase.png?sign=4c21c5927c091dcc4cefa20f06913ea2&t=1770572482 HTTP/2
> Host: phira-cdn.5wyxi.com
> User-Agent: curl/8.5.0
> Accept: */*
>
< HTTP/2 200
< content-type: image/png
< date: Sun, 08 Feb 2026 17:41:23 GMT
< etag: "028e24f6968bffeb77a98a0833b66573"
< server: tencent-cos
< x-cos-hash-crc64ecma: 4951967518000076514
< x-cos-request-id: Njk4OGNhYzNfMWM0ZjBmMWVfMjVmNF8xMDliMjBj
< last-modified: Sun, 08 Feb 2026 17:37:43 GMT
< content-length: 881317
< accept-ranges: bytes
< x-nws-log-uuid: 765378629697555668
< x-cache-lookup: Cache Miss
<
Warning: Binary output can mess up your terminal. Use "--output -" to tell
Warning: curl to output it to your terminal anyway, or consider "--output
Warning: <FILE>" to save to a file.
* Failure writing output to destination
* Connection #1 to host phira-cdn.5wyxi.com left intact
If the image camo is down again, please consider to add the image to GitHub repo and direct to it plz test in incognito mode or Ctrl-F5 to refresh the cache

Outdated Screenshot

Also, the screenshot is not latest. But the UI is similar, so it's okay to keep it.

@YuevUwU YuevUwU mentioned this pull request Feb 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant