Even though I rolled back to before I did all that which has me weirded out
by user 103054507105067008
Even though I rolled back to before I did all that which has me weirded out
by user 103054507105067008
Is the server still running on http?
It was complaining that the port was already in use which would be why then - I closed all terminals on windows but might have been a node.js process still running in task manager
by user 103054507105067008
What can we do about this SSL issue though?
by user 103054507105067008
I am now assuming that although I took out SSL, I still had mkcert plugin installed that may have been handling some SSL stuff and perhaps the two just don’t work together. As when I took out mkcert the server didn’t want to load in chrome and when I rolled back to before I added mkcert and removed SSL then I had the same issue
by user 103054507105067008
Ok so this works great for me - without basicSSL I am assuming mkcert is handling SSL instead Hope this helps others!
by user 103054507105067008