-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01.09.2014 10:30, Pete Stephenson wrote:
> Hi, > > Your server is listening on ports 11371 in addition to 80. Is this > what you intended? > > Also, the suggested membership line is incorrect: you specified > port 80 as the recon port. According to > http://keys.i2p-projekt.de/pks/lookup?op=stats your server is > listening to port 11370 for recon traffic. > > Assuming you intend to listen to port 11370 for recon traffic, the > correct line would be: keys.i2p-projekt.de 11370 # echelon > <[email protected]> 0x4A9B1723 > > That said, I've added your server as a peer (assuming you intend > to listen for recon on 11370). You can add mine to your membership > file as: > > ams.sks.heypete.com 11370 # Pete Stephenson <[email protected]> > 0x85EB9F44 Hi! The public reachable port is 80 via apache2 proxy on a vhost. The internal sks port is still 11370/11371, as port 80/443 is in use by Apache2 with different vhosts. So I cannot set SKS to listen on port 80. Ports 11370/11371 are closed in firewall and will only be opened for the syncing sks servers addresses. Yeah, a bit confusing, but if I want to run a SKS server without need to add ports to the address in browser, thats the solution I came up with. I will add your server to mine and test, thank you so far. > Cheers! -Pete echelon -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (MingW32) iEYEARECAAYFAlQEPsMACgkQmWhuE0qbFyMHLwCbBx+iKui41lfvcpi1/EJHcYD7 XjUAn2whDRRhBbUCx1YB8qHYmKL73yhq =UOTb -----END PGP SIGNATURE----- _______________________________________________ Sks-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/sks-devel
