Moritz Wirth
2018-05-21 14:01:58 UTC
Letsencrypt probably forwards port 80/port 11371 to 443, you can solve that if you add another server section for port 11371 (and port 80) where you handle the requests.
Traffic on port 11371 should remain unencrypted so rewriting it to https is not allowed
Sent from my iPhone
redirect for 11371 to 443
fwiw, I didn't add it to repo initially, but it is part of
https://git.sumptuouscapital.com/?p=sks-keyservers-pool.git;a=commitdiff;h=0a3962f591d2206aebd739bd4bec90809cc93822;hp=debbac15b210f4b9ced2235a8d3f0da1d3c4f144
Hello people,
Kristian thanks for the reply.
I do not understand what has happened, apart from finding some lines added by Certbot (leysencrypt) in nginx.conf, no change has been made to that server since the beginning of its implementation.
What can I do to solve it?
Does that problem affect the rest of the pool?
That server runs only nginx and sks, there are no other services that can affect sks.
The strangest thing is that it keeps synchronizing with other servers, I see it in recon.log and the error "POST / pks / hashquery HTTP / 1.0" 301 "no longer appears.
If you think it is not worth fixing it and removing this server from the pool, I will withdraw it and save the cost of hosting and maintenance and also remove a problem from my head that I already have more than enough.
I modified the nginx configuration file (/etc/nginx/nginx.conf) a bit to try to solve the problem, I do not know what else I can do, if someone is encouraged to help me I will appreciate it since it is a pity to leave this server outside the pool.
sincerely
Paul Fontela
--
Paul Fontela
_______________________________________________
Sks-devel mailing list
https://lists.nongnu.org/mailman/listinfo/sks-devel
Traffic on port 11371 should remain unencrypted so rewriting it to https is not allowed
Sent from my iPhone
Now we just need to find out why the server a.0.keysnode.ispfontela.es
on the list https://sks-keyservers.net/status/ has disappeared, I guess
that will be a matter of time.
This server I explicitly added to blacklist for misbehaving withon the list https://sks-keyservers.net/status/ has disappeared, I guess
that will be a matter of time.
redirect for 11371 to 443
https://git.sumptuouscapital.com/?p=sks-keyservers-pool.git;a=commitdiff;h=0a3962f591d2206aebd739bd4bec90809cc93822;hp=debbac15b210f4b9ced2235a8d3f0da1d3c4f144
Kristian thanks for the reply.
I do not understand what has happened, apart from finding some lines added by Certbot (leysencrypt) in nginx.conf, no change has been made to that server since the beginning of its implementation.
What can I do to solve it?
Does that problem affect the rest of the pool?
That server runs only nginx and sks, there are no other services that can affect sks.
The strangest thing is that it keeps synchronizing with other servers, I see it in recon.log and the error "POST / pks / hashquery HTTP / 1.0" 301 "no longer appears.
If you think it is not worth fixing it and removing this server from the pool, I will withdraw it and save the cost of hosting and maintenance and also remove a problem from my head that I already have more than enough.
I modified the nginx configuration file (/etc/nginx/nginx.conf) a bit to try to solve the problem, I do not know what else I can do, if someone is encouraged to help me I will appreciate it since it is a pity to leave this server outside the pool.
sincerely
Paul Fontela
--
Paul Fontela
_______________________________________________
Sks-devel mailing list
https://lists.nongnu.org/mailman/listinfo/sks-devel