27
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
0
2y
0
2y
Christian Tietze

@feditips Started with a stock standard Chromium "Site cannot be reached" for 2 seconds, then loaded just fine. Might be a browser bug for all I know, or recently updated DNS and outdated cache 🤷

1
2y
Grant

@feditips Working fine for me. :)

0
2y
Luc

@feditips It works and it looks great 👍👍👍

0
2y
0
2y
Sarcasmo220

@feditips At first I got secure connectipn failed but O tried it again a minute later and it worked

0
2y
Replies