ERR_SSL_PROTOCOL_ERROR when running the dev phone

[hazeerasmo99]

After running twilio dev-phone, it opens a web page, but this is all I see.

I just installed the dev phone today too. Here's the console log when I ran it.

PS C:\WINDOWS\system32> twilio dev-phone
Hello 👋 I'm your dev-phone and my name is dev-phone-<no>

✅ I'm using your profile API key.

services is deprecated. Use v1.services instead.
💻 Creating a new conversation...
services is deprecated. Use v1.services instead.
services is deprecated. Use v1.services instead.
✅ I'm using the conversation <conv> from service <serv>

💻 Creating a new sync list for call history...
services is deprecated. Use v1.services instead.
services is deprecated. Use v1.services instead.
✅ I'm using the sync service <sync service>

services is deprecated. Use v1.services instead.
💻 Deploying a Functions Service to handle incoming calls and SMS...
🧑‍💻 Creating Service
🧑‍💻 Configuring bare environment
🧑‍💻 Creating 4 Functions
🧑‍💻 Uploading 4 Functions
🧑‍💻 Creating 0 Assets
🧑‍💻 Uploading 0 Assets
🛠 Waiting for deployment. .............
🧑‍💻 Setting environment variables
🧑‍💻 Activating deployment
✅ I'm using the Serverless Service <serverless service>

💻 Creating a new TwiMl App to allow voice calls from your browser...
✅ I'm using the TwiMl App <twimlapp>

🚀 Your local webserver is listening on port 1337
🌐 Opening http://localhost:1337/ your browser

[ayyrickay]

@hazeerasmo99 this does seem to make some sense - I think the default behavior is to use HTTP, not HTTPS, when doing local development like this. There's no benefit to securing a local server (that I can see, anyway.)

Is this a browser level configuration? It may be that we simply need to document this. Another option might be to try explicitly going to the localhost URL, instead of pointing to it with localhost.