Discussions
Categories
- 196.9K All Categories
- 2.2K Data
- 239 Big Data Appliance
- 1.9K Data Science
- 450.3K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 546 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.6K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 442 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Application Container Gulp + BrowserSync Error $PORT

I have a nodejs project which includes bower, gulp, browser-sync etc. When i deploy my project to application nodejs container it throws that error:
Application failed bind to specified port[env variable $PORT]. Application logs ...
Start:
npm install
bower install
gulp serve:dist
In my configuration file i tried:
browserSync.instance = browserSync.init({ port : 80 //also tried 3000 and nothing it always throw that error.});
Can you help me how can i solve it?
Answers
-
Are you running this in the Application Container Cloud Service? If so, you need to bind to the HTTP port specified via: process.env.PORT
The load balancer will route from the internet facing port, 443 for SSL, to the internal port or ports depending on the number of instances you're running.
-
A similar problem vexed me with a raw
http.listen()
for a long time until @danmcghan-Oracle gave me a patch, removing the hostname parameter:- .listen(httpPort, "localhost");
+ .listen(httpPort); -
From my side I had this error because I was not using the proper version of Node JS. On your computer, type "node --version" in the command prompt, and make sure you are using the same version when provisionning your application.