I'm not trying to be cagey, or whatever, but being labeled "The Unknown Code Artist" is pretty cool:
http://metamn.io/react/updating-a-wordpress-theme-to-react/
I think the "socket access" error is the big clue. It's probably not your code (although full disclosure, it's late here, I can't sleep... so your code hit my TL;DR filter). :-)
But it definitely feels like an OS level issue and not an issue with your code. Assuming you're running some form of *nix (including MacOS), most users and OS processes are not allowed to run on any port lower than 1024, without human intervention on the config files.
Other alternative ideas:
there is another service running on the same port that you're try to dev on
some form of firewall is trying to be "helpful" by blocking whatever port you're trying to run the dev server on.
simple folder/file permissions. Whatever user your WWW server is running as... that user doesn't have proper access to the folder/files
Since the error specifically mentions ports, I'd start there. You're using an already occupied port, or you have a firewall setting blocking the port... etc.
I'm not trying to be cagey, or whatever, but being labeled "The Unknown Code Artist" is pretty cool:
http://metamn.io/react/updating-a-wordpress-theme-to-react/
And, of course, I missed the fact you're running in Azure. In that case, definitely check the firewall. Azure VMs are pretty strict about the ports that they can use. (I'm assuming you're in a VM of some sort and not an Azure Serverless Function type thing).
You can open ports from the Azure portal.... I don't remember the exact nav-path in the Azure portal, but Googling "open port on azure firewall" or some such should get you there.
It's an azure app service, not a virtual machine. It really is IIS as service for a single application to run. I'll see what possible network restrictions are there.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think the "socket access" error is the big clue. It's probably not your code (although full disclosure, it's late here, I can't sleep... so your code hit my TL;DR filter). :-)
But it definitely feels like an OS level issue and not an issue with your code. Assuming you're running some form of *nix (including MacOS), most users and OS processes are not allowed to run on any port lower than 1024, without human intervention on the config files.
Other alternative ideas:
Since the error specifically mentions ports, I'd start there. You're using an already occupied port, or you have a firewall setting blocking the port... etc.
And, of course, I missed the fact you're running in Azure. In that case, definitely check the firewall. Azure VMs are pretty strict about the ports that they can use. (I'm assuming you're in a VM of some sort and not an Azure Serverless Function type thing).
You can open ports from the Azure portal.... I don't remember the exact nav-path in the Azure portal, but Googling "open port on azure firewall" or some such should get you there.
It's an azure app service, not a virtual machine. It really is IIS as service for a single application to run. I'll see what possible network restrictions are there.