What type of hardware are you using: VPS bought online
What YunoHost version are you running: 12.1.39
How are you able to access your server: SSH
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: I made adjustments based on VDS, but I experienced the same issues even with a fresh VDS installation and a fresh YunoHost installation.
Describe your issue
Last night, I formatted the VDS four times and performed a fresh Yunohost installation each time. We kept adjusting settings, but the issue persisted. The problem is related to the domain. The domain is on CloudFlare, and it was like that before. I didn’t have any problems with my old VDS. The VDS was changed, and I thought it would be best to install it from scratch since it’s a more powerful machine than backing up and transferring. There was no domain issue on the old VDS. It could recognize the records on CloudFlare correctly. But I moved to the new VDS, and now there’s an issue where it can’t see the records. How can I fix this? I’ve been racking my brain for 3-4 days now.
Share relevant logs or error messages
New users can’t send links, sorry about that.
=================================
Base system (basesystem)
[INFO] Server hardware architecture is vmware amd64
- Server model is VMware, Inc. VMware Virtual Platform
[INFO] Server is running Linux kernel 6.1.0-42-amd64
[INFO] Server is running Debian bookworm
[INFO] Server is running YunoHost 12.1.39 (stable)
- yunohost version: 12.1.39 (stable)
- yunohost-admin version: 12.1.13 (stable)
- yunohost-portal version: 12.1.2 (stable)
- moulinette version: 12.1.3 (stable)
- ssowat version: 12.1.1 (stable)
=================================
Internet connectivity (ip)
[WARNING] DNS resolution seems to be working, but it looks like you’re using a custom /etc/resolv.conf.
- The file /etc/resolv.conf should be a symlink to /etc/resolvconf/run/resolv.conf itself pointing to 127.0.0.1 (dnsmasq). If you want to manually configure DNS resolvers, please edit /etc/resolv.dnsmasq.conf.
[SUCCESS] The server is connected to the Internet through IPv4!
- Global IP: xx.xx.xx.xx
- Local IP: xx.xx.xx.xx
[WARNING] The server does not have working IPv6.
- IPv6 should usually be automatically configured by the system or your provider if it’s available. Otherwise, you might need to configure a few things manually as explained in the documentation here: link
=================================
DNS records (dnsrecords)
[ERROR] Some DNS records are missing or incorrect for domain maindomain.tld (category basic)
- Please check the documentation at link if you need help configuring DNS records.
- According to the recommended DNS configuration, you should add a DNS record with the following info.
Type: A
Name: @
Value: xx.xx.xx.xx
[ERROR] Some DNS records are missing or incorrect for domain maindomain.tld (category mail)
- Please check the documentation at link if you need help configuring DNS records.
- According to the recommended DNS configuration, you should add a DNS record with the following info.
Type: MX
Name: @
Value: 10 maindomain.tld. - According to the recommended DNS configuration, you should add a DNS record with the following info.
Type: TXT
Name: @
Value: “v=spf1 a mx -all” - According to the recommended DNS configuration, you should add a DNS record with the following info.
Type: TXT
Name: mail._domainkey
Value: “v=DKIM1; h=sha256; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDkilIOP/8seMttSIiPjHuoOk9QFS92b8k313ne8uBKjaUyKnVFPMAyqzHdHsY9Tfkxjbqt5H+tPEsFUFq9vBRR4BxmI8so65Uh8M9FQZxG3ndlehCZIPhvVI1zDhAtEx1d6WGbcEBIAiaLpsdEXIdLsRhPHri9V9gNl1Qag9IJSwIDAQAB” - According to the recommended DNS configuration, you should add a DNS record with the following info.
Type: TXT
Name: _dmarc
Value: “v=DMARC1; p=none”
[WARNING] Some DNS records are missing or incorrect for domain maindomain.tld (category extra)
- Please check the documentation at link if you need help configuring DNS records.
- According to the recommended DNS configuration, you should add a DNS record with the following info.
Type: A
Name: *
Value: xx.xx.xx.xx - According to the recommended DNS configuration, you should add a DNS record with the following info.
Type: CAA
Name: @
Value: 0 issue "-letsencrypt.org - "
[WARNING] Unable to check the expiration date for some domains
- The domain maindomain.tld doesn’t exist in WHOIS database or is expired!
=================================
Ports exposure (ports)
[SUCCESS] Port 22 is reachable from the outside.
- Exposing this port is needed for admin features (service ssh)
[SUCCESS] Port 25 is reachable from the outside.
- Exposing this port is needed for email features (service postfix)
[SUCCESS] Port 80 is reachable from the outside.
- Exposing this port is needed for web features (service nginx)
[SUCCESS] Port 443 is reachable from the outside.
- Exposing this port is needed for web features (service nginx)
[SUCCESS] Port 587 is reachable from the outside.
- Exposing this port is needed for email features (service postfix)
[SUCCESS] Port 993 is reachable from the outside.
- Exposing this port is needed for email features (service dovecot)
=================================
Web (web)
[SUCCESS] Domain maindomain.tld is reachable through HTTP from outside the local network.
=================================
Email (mail)
[SUCCESS] The SMTP mail server is able to send emails (outgoing port 25 is not blocked).
[SUCCESS] The SMTP mail server is reachable from the outside and therefore is able to receive emails!
[ERROR] No reverse DNS is defined in IPv4. Some emails may fail to get delivered or be flagged as spam.
- You should first try to configure reverse DNS with maindomain.tld in your internet router interface or your hosting provider interface. (Some hosting providers may require you to send them a support ticket for this).
- Some providers won’t let you configure your reverse DNS (or their feature might be broken…). If you are experiencing issues because of this, consider the following solutions:
- Some ISP provide the alternative of using a mail server relay though it implies that the relay will be able to spy on your email traffic.
- A privacy-friendly alternative is to use a VPN with a dedicated public IP to bypass this kind of limits. See link
- Or it’s possible to switch to a different provider
[SUCCESS] The IPs and domains used by this server do not appear to be blocklisted
[SUCCESS] 0 pending emails in the mail queues
=================================
Services status check (services)
[SUCCESS] Service dnsmasq is running!
[SUCCESS] Service dovecot is running!
[SUCCESS] Service fail2ban is running!
[SUCCESS] Service nftables is running!
[SUCCESS] Service nginx is running!
[SUCCESS] Service opendkim is running!
[SUCCESS] Service postfix is running!
[SUCCESS] Service slapd is running!
[SUCCESS] Service ssh is running!
[SUCCESS] Service yunohost-api is running!
[SUCCESS] Service yunohost-portal-api is running!
[SUCCESS] Service yunomdns is running!
=================================
System resources (systemresources)
[SUCCESS] The system still has 11 GiB (92%) RAM available out of 12 GiB.
[SUCCESS] The system has 975 MiB of swap!
- Please be careful and aware that if the server is hosting swap on an SD card or SSD storage, it may drastically reduce the life expectancy of the device.
[SUCCESS] Storage / (on device /dev/sda1) still has 90 GiB (97.3%) space left (out of 92 GiB)!
=================================
System configurations (regenconf)
[WARNING] Configuration file /etc/apt/sources.list.d/extra_php_version.list appears to have been manually modified.
- This is probably OK if you know what you’re doing! YunoHost will stop updating this file automatically… But beware that YunoHost upgrades could contain important recommended changes. If you want to, you can inspect the differences with ‘yunohost tools regen-conf apt --dry-run --with-diff’ and force the reset to the recommended configuration with ‘yunohost tools regen-conf apt --force’
[WARNING] Configuration file /etc/apt/sources.list.d/yarn.list appears to have been manually modified.
- This is probably OK if you know what you’re doing! YunoHost will stop updating this file automatically… But beware that YunoHost upgrades could contain important recommended changes. If you want to, you can inspect the differences with ‘yunohost tools regen-conf apt --dry-run --with-diff’ and force the reset to the recommended configuration with ‘yunohost tools regen-conf apt --force’
=================================
Applications (apps)
[SUCCESS] All installed apps respect basic packaging practices