10.10.10.10 or 192.158.255.1 or whatever your local network or even WAN is using. In the host file we can obviously deal with higher-level of TCP/IP. #MACOS SERVER VIRTUAL HOSTS MAC#MAC here of course does not at all refer to Mac as in Apple etc, but to networking since the 60ies or so, an acronoymfor Machine Address C…? etc. Q: is it possible to somehow bind fa20::907:1051:3cc9:0a33 or other, presumably so-called MAC-axresses aka hardware addresees per interface. However, with “ssh CHOSENBONJOURNAME.local” working too, I am ASKING A QUESTION here which seems beyond trivial Google search research. #MACOS SERVER VIRTUAL HOSTS MAC OS X#So, with ping CHOSENBONJOURNAME.local specifically on Mac OS X and macOS we can fetch the IP address. (in the environment, using eg “env | grep SSH” on macOS High Sierra, and surely many other platforms for that matter, incl beyond BSD, Darwin, macOS etc ALTHOUGH the Bonjour serviices maybe are not available? On QNAP NAS, for example it is though, under the name avahi, if my memory serves…) What’s the best way for me to proceed, to get and maintain a Let’s Encrypt certificate for my port 443 instance? If there’s a way for me to get the certificate some other way, I can easily use the Server app to add it to my site.Is it possible to use the address given from eg I don’t want to muck with the configuration too much because that might confuse the Server app. another httpd instance using /Library/Server/Web/Config/apache2/httpd_server_app.conf, which loads individual files from /Library/Server/Web/Config/apache2/sites for each individual site and handles the ports forwarded to it from the above instanceĪt first I was only aware of the second one of these, but the first one is definitely what runs afoul of that limitation.an httpd instance using /Library/Server/Web/Config/Proxy/apache_nf, which defines a VirtualHost for port 80 and another for port 443, and each of these VirtualHosts proxies to a different port.It may be entirely possible that that bit about “a file with multiple vhosts” is what’s causing trouble, because as I try to decipher the way that macOS Server sets things up, it looks like I have: Library/Server/Web/Config/apache2/sites/0000_127.0.0.1_34580_.conf: ServerAlias Īnyone have any suggestions? Are there other ways to configure this that I should fall back to? I don’t see many reports of people using it on macOS. And I do have ServerAlias entries set up in the config files: $ grep ServerAlias /Library/Server/Web/Config/apache2/sites/*.conf My DNS A record for this domain has the correct IP address. Same thing happens if I enter “ as the domain. Received 2 certificate(s), firstĬertificate had names "To fix these errors, please make sure that your domain name wasĮntered correctly and the DNS A record(s) for that domain The following errors were reported by the server:ĭetail: Incorrect validation certificate for tls-sni-01 challenge.Įįrom 216.53.249.115:443. Received 2 certificate(s), first certificate had names "IMPORTANT NOTES: (tls-sni-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Incorrect validation certificate for tls-sni-01 challenge. Please specify ServerName or ServerAlias in the Apache config, or split vhosts into separate files.įailed authorization procedure. No vhost exists with servername or alias of: (or it's in a file with multiple vhosts, which Certbot can't parse yet). I enter “ ”, then it tells me: Obtaining a new certificate Name(s) (comma and/or space separated) (Enter 'c' to cancel): No names were found in your configuration files. When I run “certbot -apache”, it first says: Saving debug log to /var/log/letsencrypt/letsencrypt.log I manage the site through the Apple macOS “Server” application. My server is running macOS 10.12.5 / Apache 2.4.25.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |