mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 05:26:03 +03:00
[GH-ISSUE #129] mkcert ruined my localhost:8080 #73
Labels
No labels
TLS stack issue
Windows
bug
duplicate
duplicate
enhancement
help wanted
help wanted
pull-request
question
question
root store
waiting for info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mkcert#73
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tr1s on GitHub (Feb 5, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/129
I had to run these commands in order to get slate to work, it never worked... Then I found some hacks in the github issues of slate, it finally worked by creating some keys in my project.
Now when I run webpack-dev-server on my own personal projects using my boilerplate, localhost:8080 doesn't work anymore, none of them do. I tried doing mkcert install and mkcert localhost and it created my keys, but still nothing.. I get this below.
How do I get things back to normal? I don't want all these extra steps just to run my personal projects. All I had to do before was type "npm start" and everything was ready to go. Ever since me setting up one slate project everything else is ruined so far.
Any ideas? How can I fix this?
@FiloSottile commented on GitHub (Feb 5, 2019):
ERR_SSL_PROTOCOL_ERROR suggests that the issue has nothing to do with the certificate and key that mkcert generates, but is a problem with whatever HTTPS/TLS implementation you are using.
@tr1s commented on GitHub (Feb 5, 2019):
@FiloSottile so what do I do about this?
I know for a fact that everything was fine before I brew installed mkcert and set up this slate project. I can't even get my static freelance projects running right now. I didn't change any code whatsoever in my other projects. How do I revert back from all this?
@FiloSottile commented on GitHub (Feb 5, 2019):
I'm sorry to hear this, but it sounds like it worked before you started using HTTPS and TLS, so you have to find out what software you are using for HTTPS and TLS and what the issue with it is. mkcert does not run any code after generating the certificate and key files.
@tr1s commented on GitHub (Feb 5, 2019):
@FiloSottile Can you give me some sort of direction?
I created a webpack boilerplate, I used webpack cli/webpack-dev-server, I run npm start and everything works as it should. I have no extra software that's making me use HTTPS/TLS. I just made a config and everything worked.
Now that I have mkcert nothing works. I don't really know what you're telling me here about extra software. There is no extra software. Nothing I'm trying is fixing this so far
@FiloSottile commented on GitHub (Feb 5, 2019):
I know next to nothing about the Node.js ecosystem, but I assume you did not just run mkcert, you probably also changed some options to tell your server to load the certificate mkcert created. That's the HTTPS code that would be having issues.
(If not, have you tried loading http://localhost:8080 instead of https://?)
@tr1s commented on GitHub (Feb 5, 2019):
I went through my command history and I think these two got the slate project to work. Does that mean anything to you?
I went through the install process from the mkcert docs recently to try and override it but nothing happens. Http just get's forced to https to answer your question.
@tr1s commented on GitHub (Feb 5, 2019):
@tr1s commented on GitHub (Feb 5, 2019):
@FiloSottile is there a way I can fully revert this and delete anything and everything mkcert created? I need to abandon this slate project so I can fix everything else asap.
@tr1s commented on GitHub (Feb 6, 2019):
Feel free to close this. I had to recover my mac from the day before this happened.
@FiloSottile commented on GitHub (Feb 8, 2019):
I'm sorry to hear that. If you have further problems with HTTPS aside from the certificate itself, it looks like the name of the project you need to open an issue in is "Slate".
@skywinston commented on GitHub (Apr 10, 2019):
The solution to this problem can be found here:
https://github.com/Shopify/slate/issues/726#issuecomment-431372434
@saurabhsethi1102 commented on GitHub (Nov 26, 2020):
You can always use a private window to route to http://localhost
@iulianalbu commented on GitHub (Jul 22, 2021):
@saurabhsethi1102 Yea, your idea it's working, but for Postman not.
@tr1s I manage to fixed this issue
@Drjacky commented on GitHub (Feb 18, 2024):
Same here! Working with Ktor, and after this, it fixed my issue; I could see the Welcome page. Then I installed mkcert and it ruined my setup! Uninstalling all the certs it created and itself didn't help either
Unfortunately this is no an option for me:
@Drjacky commented on GitHub (Feb 18, 2024):
In this case, you need to define a new port; not sure where and how, but the ruined address(locahost) and port is cached!
@raul-rtl commented on GitHub (Feb 28, 2024):
same here, after installing mkcert it ruined my setup, I tried iulianalbu solution but not success
@Jeffxz commented on GitHub (Apr 11, 2024):
This helped me on chrome https://stackoverflow.com/questions/25277457/google-chrome-redirecting-localhost-to-https
What I did was enter
chrome://net-internals/#hsts, query for "localhost", if there is any hit then delete "localhost" and it worked for me.@MisterDr commented on GitHub (Aug 16, 2024):
In my case solution was rather simple. Since I am using VSCode and it has ugly habit to forward the ports on whatever it sees at the console, I simply removed forwarded ports. Double check to see if anything else is listening on your development port.