I'm getting this error:
Parsing account key... Parsing CSR... Registering account... Already registered! Verifying moreinter.net... Traceback (most recent call last): File "/usr/libexec/webmin/webmin/acme_tiny.py", line 235, in main(sys.argv[1:]) File "/usr/libexec/webmin/webmin/acme_tiny.py", line 231, in main signed_crt = get_crt(args.account_key, args.csr, args.acme_dir, args.dns_hook, args.cleanup_hook, log=LOGGER, CA=args.ca) File "/usr/libexec/webmin/webmin/acme_tiny.py", line 184, in get_crt domain, challenge_status)) ValueError: moreinter.net challenge did not pass: {u'status': u'invalid', u'keyAuthorization': u'OHnn7BAxjcCgBQF-1jb5BsxVSLHYG_iK-wTV0zXqpdo.-0dBn0NYEO5O3mlX1Fzfn7Uf5pHwA4E1naPp30q9zh8', u'uri': u'https://acme-v01.api.letsencrypt.org/acme/challenge/PTdi_P817HpGumHEDMjy...', u'token': u'OHnn7BAxjcCgBQF-1jb5BsxVSLHYG_iK-wTV0zXqpdo', u'error': {u'status': 403, u'type': u'urn:acme:error:unauthorized', u'detail': u'No TXT records found for DNS challenge'}, u'type': u'dns-01'}
This a fresh install of Virtualmin with nginx and php7.1. I haven't installed any other version of Let's Encrypt but just used this one.
Comments
Submitted by Kershrew on Sat, 05/20/2017 - 14:44 Comment #1
I went to my url and discovered I was getting a 400 Bad Request The plain HTTP request was sent to HTTPS port. After a quick google I went into /etc/nginx/nginx.conf and commented out the line: ssl on. Restarted nginx. This fixed my site and fixed this issue as well allowing Let's Encrypt to work.
Except the last thing it tried to do resulted in this: Applying Nginx configuration .. .. restart failed :
Dunno what this implies?
Submitted by JamieCameron on Sat, 05/20/2017 - 15:03 Comment #2
The initial error actually looks more like a DNS problem - is your DNS domain hosted by your Virtualmin system?
Submitted by Kershrew on Sun, 05/21/2017 - 14:37 Comment #3
I don't think so, it's on OVH and I have a named server running and all the dns stuff that goes with it. Am I missing something? I change my hostname to the first domain I'm going to be putting on the server as well if that makes a difference so it changes from the ovh assigned default.
Edit: Although I have progressed passed this issue by adding 'nameserver 127.0.0.1' to resolv.conf but I haven't really restarted anything since doing that except postfix.
Edit2: This is the next error I get : 'A problem was found with your Postfix virtual maps : No map sources were found in the Postfix configuration'. :p
Submitted by Kershrew on Sun, 05/21/2017 - 14:43 Comment #4
Submitted by Kershrew on Sun, 05/21/2017 - 14:58 Comment #5
Fixed that by adding 'virtual_alias_maps = hash:/etc/postfix/virtual' to /etc/main.cnf
Now I get: Automatic BCCing of outgoing email cannot be enabled unless a BCC map is defined in the Postfix Mailserver module, or manually in the Postfix configuration file. Otherwise it must be turned off on the module configuration page.
Edit: Starting to think it's my fault in it's initial configuration now, lots of mail related stuff isn't setup and I installed postfix before I ran the installer
Submitted by JamieCameron on Sun, 05/21/2017 - 20:05 Comment #6
How did you install Virtualmin originally? From those errors, it sounds like maybe the our install script wasn't used?
Submitted by Kershrew on Mon, 05/22/2017 - 03:56 Comment #7
wget http://software.virtualmin.com/gpl/scripts/install.sh
This is what I used.
Edit: Although I do usually get errors around the clamav setup and have to ctrl+c that part of it and let it carry on.
Submitted by andreychek on Mon, 05/22/2017 - 09:32 Comment #8
Is it possible that the install script had errored out before completing?
As the error you're seeing above suggests that some things that are normally added to the Postfix main.cf file during installation hadn't been put there.
However, you can try adding this line to your main.cf file to correct that:
virtual_alias_maps = hash:/etc/postfix/virtual
And then restart Postfix.
Submitted by Kershrew on Mon, 05/22/2017 - 14:59 Comment #9
This fixes the postfix error, I just did another install and have had the same issue requiring me to manually add this line to main.cnf. Maybe this is an issue with centos 7?
Submitted by andreychek on Mon, 05/22/2017 - 15:19 Comment #10
I'm actually doing a CentOS 7 install now onto one of my personal servers, and that line was correctly added.
Is there any chance you could post your /root/virtualmin-install.log file?