

Finally, Switzerland generally will not assist prosecutions from countries without fair justice systems,” the ProtonMail CEO added. “The Swiss legal system, while not perfect, does provide a number of checks and balances, and it’s worth noting that even in this case, approval from 3 authorities in 2 countries was required, and that’s a fairly high bar which prevents most (but obviously not all) abuse of the system. On the other hand, Yen also highlighted that despite the fact that they were forced to comply with Swiss law, the Swiss legal system is far more robust than the legal systems of other countries. However, the ProtonMail CEO said that an accompanying gag order also prevented the company from disclosing this incident to the user while the investigation was underway. “Under Swiss law, it is also obligatory for the suspect to be notified that their data was requested, which is not the case in most countries,” he added. “There was no legal possibility to resist or fight this particular request,” ProtonMail CEO Andy Yen said earlier today. The order effectively forced the company to log the IP address used by the French activist to log into their ProtonMail inbox. “In this case, Proton received a legally binding order from the Swiss Federal Department of Justice which we are obligated to comply with,” a ProtonMail spokesperson wrote on Reddit over the weekend. ProtonMail said it couldn’t fight the legal order Last week, the website Paris Luttes (Paris Struggles) revealed that French police worked through Europol to contact the Swiss government and asked for help in obtaining details about the email address owner’s identity. The group apparently used a ProtonMail email address to organize their protests ( a detail that came to the attention of the real estate companies and French police, which was called in to evacuate the group and investigate its members.
#Proton email alert unable to connect to the server series#
The incident is a complex one and is related to a series of anti-gentrification protests that took place in Paris in the summer and fall of 2020 when a group of activists named Youth for Climate forcibly occupied a series of squares and buildings in the Paris district of Place Sainte Marthe, in order to protest companies buying real estate and hiking up rent prices up to four times for local residents. Case related to anti-gentrification protests in France However, in a Reddit comment on Sunday and in a blog post published earlier today, ProtonMail said it was cornered by Swiss authorities earlier this year. The incident, which came to light over the weekend, has caused some unrest among the company’s users as ProtonMail had boasted numerous times in its public marketing campaigns about its no-log policies. Switzerland-based email provider ProtonMail said it was forced to log the IP address of one of its customers after it received a legally binding order from the Swiss government that it couldn’t legally appeal or decline.

Even if you whitelist some ProtonVPN IP addresses with your firewall, that is still not enough because any user would still be able to reach your database through the very same ProtonVPN IP address.Īnyway, I suggest you try the following servers since MySQL and PostgreSQL ports (33) are opened on them for the time being:ĭE#12 (Germany) US-NY#6 (United States) SG#28 (Singapore)Īlso, we are working on a solution to provide dedicated IPs in the upcoming period, but I cannot give you any specific time-frame for that to happen.ProtonMail forced to collect an activist’s IP address in police investigation Normally, any user connected to the same ProtonVPN server would have the same authorization to access the database you are willing to connect to unless there are additional security measures in place, so this is not recommended and insecure. Please be informed that outgoing connections to some database-related ports are currently being blocked on most of our servers for anti-abuse reasons, so this could be the reason you are experiencing such an issue. I got the following response from support when I had similar issues with MySQL (a year ago):
