Hello,
Post by Egor SkriptunoffI'm getting 404 too.
www.getcujo.com is located at Amazon Web Services, and millions of Amazon servers' IP addresses have been blocked in Russia while attempting to block Telegram messenger.
Alas, the Russian government is the shame of Russia.
Just for the record:
$ curl -D - https://www.getcujo.com/
HTTP/2 404
date: Tue, 04 Sep 2018 09:50:05 GMT
content-type: text/html
cache-control: no-store
x-zen-fury: 7fb34992febaff8fcbe3f16da6b3660aaae9f864
server: ZENEDGE
access-control-allow-origin: https://www.getcujo.com
x-xss-protection: 1; mode=block
strict-transport-security: max-age=31536000; preload
<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
$ curl --http1.1 -D - https://www.getcujo.com/
HTTP/1.1 404 Not Found
Date: Tue, 04 Sep 2018 09:51:06 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: keep-alive
Cache-Control: no-store
X-Zen-Fury: 3dc952fc1711bbc8294d5a476db07e1327c67495
Server: ZENEDGE
Access-Control-Allow-Origin: https://www.getcujo.com
X-XSS-Protection: 1; mode=block
Strict-Transport-Security: max-age=31536000; preload
<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
Headers and message really look like an error page originating from
the server itself, not like one of the pages generated by ISP filters.
I'm afraid our government isn't directly responsible for this, it's
more likely that the folks that people you chose to host the workshop
don't like our folks:).
Best regards,
--
DoubleF