-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't open website because it's "insecure" #56
Comments
oh its fixed now its safe |
I'm pretty sure if you click advanced it says continue? but I'm not an expert on error's soo |
here (I don't know if his worked because my snip and sketch is broken) |
Same issue here now. Looks like the certificate expired today. |
@SuperDuperRob hey so uh i'm not super tech savvy and have no idea what any of this means, but is it still safe to access? i have school music projects i have to work on lol |
Yes, it is still safe. Just never share personal information with websites that have a security problem like that. It means that the data you send them might be visible to people in transit, or that you are sending data to an entirely different website. For the song maker, though, you're not sharing personal information so is not really a concern. Just highly unprofessional and careless maintenance by Google who should do better to support an application that music learners and teachers around the world depend on. |
@TatterCat Could you tell me how to run the project on local machine. While doing npm install it says all the files required are deprecated. |
It is still hacked I am contacting Google and they even though it is working it is the hacker working it not them |
(I'm on Chrome) I am unable to open chrome music labs, and says "Your connection is not private
Attackers might be trying to steal your information from musiclab.chromeexperiments.com (for example, passwords, messages, or credit cards)." I know Google wouldn't be trying to steal my information, is there a way to fix this?
Edit: On Microsoft Edge, it says the same thing but allows me to continue anyways. When I do continue, it shows the 404 screen.
The text was updated successfully, but these errors were encountered: