Server status - News regarding the servers

Hi,

both servers in Huenenberg (Switzerland) have been removed for security reasons. To give the hoster a couple of days to react, we will publish the details later. As you might have guessed from the thread (in the german forum section), this is about ILO which the hoster has still enabled despite numerous warnings.

Huenenberg2 did not survive a reboot the day before yesterday, and is gone already.
Huenenberg1 is still online, but all logins on this server have been deleted. So there is no login with your Perfect Privacy login credentials possible.

Huenenberg1 will stay online until the termination of the contract is completed, the username and password are "test".
All DNS names are of course also gone since this is automated. If you want to use it:
IP: 176.10.115.98
Additional IP addresses: 176.10.115.100,176.10.115.101,176.10.115.102,176.10.115.103,176.10.115.104,176.10.115.105,176.10.115.106,176.10.115.107,176.10.115.108, 176.10.115.109,176.10.115.110,176.10.115.111,176.10.115.112,176.10.115.113,176.10.115.114,176.10.115.115,176.10.115.116,176.10.115.117, 176.10.115.118,176.10.115.119, 176.10.115.120,176.10.115.121,176.10.115.122,176.1 0.115.123,176.10.115.124,176.10.115.125,176.10.115.126

Certificates etc. stayed as they have been before.

Have fun,

Daniel
 
Regarding servers in Switzerland: We have ordered two 100mbit/s servers there at different hosters to help mitigating abuse. Downloaders will surely prefer servers with gigabit connection, and we are running out of hosters in Switzerland. Our members who need an IP address from there for services like Zattoo this should be enough. But of course we will monitor bandwidth usage and stability of the servers and add more if necessary.
 
As previously mentioned in some threads, Hulu does not work anymore with the IP addresses of the server in Washington. We have therefore terminated the contract for this server, so it will only continue to run until july 31st. We have ordered a new server in New Jersey, and hope Hulu etc. will work with it's IP addresses.
 
The servers in London are getting exchanged right now and should be up again soon with some fresh IP addresses too. We asked for some new IP addresses for our servers there, and got offered an upgrade of the servers too, so we took the opportunity.
 
Bucharest is up, but still not operational. We are in contact with the datacenter and working on resolving the issue.
 
We are still waiting on the second server in Switzerland. We have got an IP address range, but no login data yet.
 
The second server in Switzerland is now online, it is located in the same datacenter as the servers we had with Datasource, but it is from a different hoster.
 
Unfortunately there are issues with the Squid http proxies currently, we will fix this as soon as possible.
 
The issue with the Squid http proxies has been resolved, we apologize for any inconveniences this may have caused!
 
PP Daniel said:
The second server in Switzerland is now online, it is located in the same datacenter as the servers we had with Datasource, but it is from a different hoster.
Click to expand...
Correction: We recieved an email from our new hoster explaining they have their own exclusive datacenter, which is where our server is located.
 
Expect the servers in Rotterdam, Netherlands to be unavailable for a couple of hours within the next days, as we are going to exchange them for new ones.
 
hellabrunn said:
Server Israel has been down for several days, but it's still listed as online in the server list.
Click to expand...

israelu

Code: 
Wed Apr  5 08:20:06 2023 Multiple --up scripts defined.  The previously configured script is overridden.
Wed Apr  5 08:20:06 2023 Multiple --down scripts defined.  The previously configured script is overridden.
Wed Apr  5 08:20:06 2023 OpenVPN 2.4.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 19 2021
Wed Apr  5 08:20:06 2023 library versions: OpenSSL 1.1.1f  31 Mar 2020, LZO 2.10
Wed Apr  5 08:20:06 2023 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Wed Apr  5 08:20:06 2023 Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
Wed Apr  5 08:20:06 2023 Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
Wed Apr  5 08:20:06 2023 Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
Wed Apr  5 08:20:06 2023 Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
Wed Apr  5 08:20:06 2023 TCP/UDP: Preserving recently used remote address: [AF_INET]82.81.85.231:4433
Wed Apr  5 08:20:06 2023 Socket Buffers: R=[212992->212992] S=[212992->212992]
Wed Apr  5 08:20:06 2023 UDPv4 link local: (not bound)
Wed Apr  5 08:20:06 2023 UDPv4 link remote: [AF_INET]82.81.85.231:4433
Wed Apr  5 08:20:06 2023 TLS: Initial packet from [AF_INET]82.81.85.231:4433, sid=2a230df5 9540f575
Wed Apr  5 08:20:06 2023 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Wed Apr  5 08:20:06 2023 VERIFY OK: depth=1, C=CH, ST=Zug, L=Zug, O=Perfect Privacy, CN=Perfect Privacy, emailAddress=admin@perfect-privacy.com
Wed Apr  5 08:20:06 2023 VERIFY ERROR: depth=0, error=certificate has expired: C=CH, ST=Zug, O=Perfect Privacy, CN=Server_jerusalem.perfect-privacy.com, emailAddress=admin@perfect-privacy.com
Wed Apr  5 08:20:06 2023 OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed
Wed Apr  5 08:20:06 2023 TLS_ERROR: BIO read tls_read_plaintext error
Wed Apr  5 08:20:06 2023 TLS Error: TLS object -> incoming plaintext read error
Wed Apr  5 08:20:06 2023 TLS Error: TLS handshake failed
Wed Apr  5 08:20:06 2023 SIGUSR1[soft,tls-error] received, process restarting
Wed Apr  5 08:20:06 2023 Restart pause, 5 second(s)
Wed Apr  5 08:20:11 2023 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Wed Apr  5 08:20:11 2023 TCP/UDP: Preserving recently used remote address: [AF_INET]82.81.85.231:4433
Wed Apr  5 08:20:11 2023 TCP/UDP: Preserving recently used remote address: [AF_INET]82.81.85.231:4433
Wed Apr  5 08:20:11 2023 Socket Buffers: R=[212992->212992] S=[212992->212992]
Wed Apr  5 08:20:11 2023 UDPv4 link local: (not bound)
Wed Apr  5 08:20:11 2023 UDPv4 link remote: [AF_INET]82.81.85.231:4433
Wed Apr  5 08:20:11 2023 TLS: Initial packet from [AF_INET]82.81.85.231:4433, sid=63cd3be4 12781548
Wed Apr  5 08:20:11 2023 VERIFY OK: depth=1, C=CH, ST=Zug, L=Zug, O=Perfect Privacy, CN=Perfect Privacy, emailAddress=admin@perfect-privacy.com
Wed Apr  5 08:20:11 2023 VERIFY ERROR: depth=0, error=certificate has expired: C=CH, ST=Zug, O=Perfect Privacy, CN=Server_jerusalem.perfect-privacy.com, emailAddress=admin@perfect-privacy.com
Wed Apr  5 08:20:11 2023 OpenSSL: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed
Wed Apr  5 08:20:11 2023 TLS_ERROR: BIO read tls_read_plaintext error
Wed Apr  5 08:20:11 2023 TLS Error: TLS object -> incoming plaintext read error
Wed Apr  5 08:20:11 2023 TLS Error: TLS handshake failed
Wed Apr  5 08:20:11 2023 SIGUSR1[soft,tls-error] received, process restarting
Wed Apr  5 08:20:11 2023 Restart pause, 5 second(s)
^CWed Apr  5 08:20:12 2023 SIGINT[hard,init_instance] received, process exiting
 
You must log in or register to reply here.
Back
Top