Issue with www. subdomain of site hosted on codeberg pages #1855

hossein commented 2025年04月19日 14:28:52 +02:00

Comment

Hi!

Despite the fact that my .domains file has both my domain and its www subdomain, and the fact that I have set up a correct CNAME and TXT record for my domain

$ dig www.hossein.me
;; ANSWER SECTION:
www.hossein.me.		300	IN	CNAME	main.pages.hossein.codeberg.page.
main.pages.hossein.codeberg.page. 300 IN A	217.197.84.141

I have a problem where a TLS cert is not issued for my www subdomain, and I also get "Failed Dependency (Error 424)! "could not obtain repo owner from custom domain"" after accepting the TLS security risk.

Thanks in advance.

### Comment Hi! Despite the fact that my [.domains file](https://codeberg.org/hossein/pages/src/branch/main/.domains) has both my domain and its www subdomain, and the fact that I have set up a correct CNAME and TXT record for my domain ``` $ dig www.hossein.me ;; ANSWER SECTION: www.hossein.me. 300 IN CNAME main.pages.hossein.codeberg.page. main.pages.hossein.codeberg.page. 300 IN A 217.197.84.141 ``` I have a problem where a TLS cert is not issued for my www subdomain, and I also get "Failed Dependency (Error 424)! "could not obtain repo owner from custom domain"" after accepting the TLS security risk. Thanks in advance.

Gusted commented 2025年04月19日 14:31:53 +02:00

Please check again.

Please check again.

hossein commented 2025年04月19日 15:53:50 +02:00

Nope, it still doesn't work. Here's curl -4 -Lv https://www.hossein.me:

* Host www.hossein.me:443 was resolved.
* IPv6: (none)
* IPv4: 217.197.84.141
* Trying 217.197.84.141:443...
* GnuTLS priority: NORMAL:-ARCFOUR-128:-CTYPE-ALL:+CTYPE-X509:-VERS-SSL3.0
* ALPN: curl offers h2,http/1.1
* found 152 certificates in /etc/ssl/certs/ca-certificates.crt
* found 458 certificates in /etc/ssl/certs
* SSL connection using TLS1.3 / ECDHE_RSA_AES_128_GCM_SHA256
* server certificate verification OK
* server certificate status verification SKIPPED
* SSL: certificate subject name (*.codeberg.page) does not match target hostname 'www.hossein.me'
* closing connection #0
curl: (60) SSL: certificate subject name (*.codeberg.page) does not match target hostname 'www.hossein.me'
More details here: https://curl.se/docs/sslcerts.html

I even tried using a web proxy:
https://www.croxyproxy.com/

Even there it fails.

Nope, it still doesn't work. Here's `curl -4 -Lv https://www.hossein.me`: ``` * Host www.hossein.me:443 was resolved. * IPv6: (none) * IPv4: 217.197.84.141 * Trying 217.197.84.141:443... * GnuTLS priority: NORMAL:-ARCFOUR-128:-CTYPE-ALL:+CTYPE-X509:-VERS-SSL3.0 * ALPN: curl offers h2,http/1.1 * found 152 certificates in /etc/ssl/certs/ca-certificates.crt * found 458 certificates in /etc/ssl/certs * SSL connection using TLS1.3 / ECDHE_RSA_AES_128_GCM_SHA256 * server certificate verification OK * server certificate status verification SKIPPED * SSL: certificate subject name (*.codeberg.page) does not match target hostname 'www.hossein.me' * closing connection #0 curl: (60) SSL: certificate subject name (*.codeberg.page) does not match target hostname 'www.hossein.me' More details here: https://curl.se/docs/sslcerts.html ``` I even tried using a web proxy: https://www.croxyproxy.com/ Even there it fails.

Gusted commented 2025年04月19日 16:08:31 +02:00

Retrieving the CNAME record gives inconsistent results for www.hossein.me according to the DNS resolver.

Retrieving the CNAME record gives inconsistent results for `www.hossein.me` according to the DNS resolver.

hossein commented 2025年04月19日 17:03:42 +02:00

@Gusted wrote in #1855 (comment):

Retrieving the CNAME record gives inconsistent results for www.hossein.me according to the DNS resolver.

You are absolutely correct.

For posterity:
I had unknowingly misconfigured my domain. If you assign a CNAME to the apex in Cloudflare it will preform CNAME flattening which means it will return A and AAAA records and not CNAME if asked about your apex.

So to sum it up: On Cloudflare, if you make a CNAME record to your apex and then make a CNAME from www. to your apex, Codeberg won't be able to find out which site it must show.

@Gusted wrote in https://codeberg.org/Codeberg/Community/issues/1855#issuecomment-3858591: > Retrieving the CNAME record gives inconsistent results for `www.hossein.me` according to the DNS resolver. You are absolutely correct. For posterity: I had unknowingly misconfigured my domain. If you assign a CNAME to the apex in Cloudflare it will preform _CNAME flattening_ which means it will return A and AAAA records and not CNAME if asked about your apex. So to sum it up: On Cloudflare, if you make a CNAME record to your apex and then make a CNAME from `www.` to your apex, Codeberg won't be able to find out which site it must show.