Twine Version: 2.9.1
I recently formatted my PC and the web version of twine is no longer opening. It’s giving a warning that it’s “not safe”. What do I do?
Twine Version: 2.9.1
I recently formatted my PC and the web version of twine is no longer opening. It’s giving a warning that it’s “not safe”. What do I do?
If you post the error page, that would help.
However, if you’re being denied access in some way, whoever’s responsible will probably sort it out on their own. It might not be related to your PC reformat. You can try waiting it out.
You also could download the offline version of Twine from GitHub and use it in the mean time. Probably this one for Windows, other ones here.
The page is white with a “not safe” warning in the URL bar. I’ll use the app until the web version is back. Thanks.
@janosbiro I believe I found the problem.
Try this link with https
instead of http
…
https://twinery.org/2
@klembot In Firefox, the link from the main page is http://twinery.org/2
and is flagged as unsafe, but in Chrome it’s using https://twinery.org/2
. I can still go to the https
address in Firefox manually and Twine works fine, but I have no idea why it’s defaulting to the unsecure http
protocol. Anyway, just FYI.
It works, thanks.
It depends on which main page you visit. If you start at http://twinery.org/, then the link is to http, but if you start at https://twinery.org/, it’s to https.
I think I got to the main page by searching Google, actually. However, I’m on a different computer right now. It’s interesting that when I click the http
link you provided, it sends me to https
automatically. So I think it’s a problem with the forced https
not working in all scenarios. Interesting.
We can’t force a HTTP → HTTPS change (yet?) because some people may have work saved in the HTTP browser version, and the HTTP and HTTPS versions of web sites don’t share local storage. If we automatically redirected to HTTPS, you would have no way to get to any data saved in the HTTP version. All that is to say that any redirect you might be seeing is probably caused by your browser.
I’ve thought about how to make a transition to only HTTP happen because HTTPS is now the norm (and for good reason), but I haven’t had any brilliant ideas on how to do it without too much effort.