Diagnosis fails at DNS step with a Python error

:uk:/:us: Message template (english)

The “support” category is meant to ask for help or troubleshooting related to installing or using YunoHost or its applications. It is not to ask assistance on general system administration, network administration or special use cases that goes beyond the scope of the project. If you wish to discuss more advanced use case, please post in the “Advanced Use Case” category.

Before posting, please :

My YunoHost server

Hardware: VPS bought online
YunoHost version: 11.2.24
I have access to my server : Through SSH and through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ?: no

Description of my issue

I cannot run the diagnosis tool in the web UI nor through SSH because the DNS Records step fails with this error in both places.

Diagnosis failed for category 'dnsrecords':
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/yunohost/diagnosis.py", line 183, in diagnosis_run
code, report = diagnoser.diagnose(force=force)
File "/usr/lib/python3/dist-packages/yunohost/diagnosis.py", line 431, in diagnose
items = list(self.run())
File "/usr/lib/python3/dist-packages/yunohost/diagnosers/12-dnsrecords.py", line 57, in run
for report in self.check_domain(
File "/usr/lib/python3/dist-packages/yunohost/diagnosers/12-dnsrecords.py", line 121, in check_domain
if self.current_record_match_expected(r):
File "/usr/lib/python3/dist-packages/yunohost/diagnosers/12-dnsrecords.py", line 220, in current_record_match_expected
key, value = param.split("=")

I pushed a fix for the next release, but this is coming from an existing DMARC record not containing any = on “your” side, sort of

1 Like

Thank you! I checked my DNS settings and I think the issue was me entering the _dmarc after the subdomain by accident. I just fixed it so I am going to try to re-run it in a bit once it’s propagated

Ah the second domain is where I messed up the _dmarc, I entered it with the domain like the MX record so it was indeed missing the =. Just fixed it and the DNS diag is running normally again

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.