Deploy a Node.js App on Shared Hosting via cPanel | Tutorial
HTML-код
- Опубликовано: 13 дек 2022
- 👉 More tutorials like this: openjavascript.info
🎓 NEW: Earn a professional certificate in web development from Meta Inc. (course links in card below) 👇
⚡ Looking for high-performance, afforable web hosting? We use HostWithLove: bit.ly/3V2RM9Q ❤️
This tutorial shows you how to deploy a Node.js App on a shared hosting account that supports Node.js apps via cPanel.
#nodejs #cpanel #sharedhosting #app #deploy #webdevelopment #tutorial
🔔 Subscribe for more tutorials just like this: / @openjavascript
⚡Web development professional certificates from Meta Inc.⚡
Front-End Developer Professional Certificate: imp.i384100.net/b3dMek
Back-End Developer Professional Certificate: imp.i384100.net/gbYorg
iOS Developer Professional Certificate: imp.i384100.net/Jr7qj2
Meta Android Developer Professional Certificate: imp.i384100.net/oeYnGo
Meta Database Engineer Professional Certificate: imp.i384100.net/BX7KGB
Website: openjavascript.info
UPDATE: The hosting provider I am using in this video (HostWithLove: bit.ly/3V2RM9Q) now allows you to run apps in Node 18.14 (and also still older versions, if you prefer).
I highly recommend them if you do not already have shared hosting space for their great support and fair pricing.
Plese, where is the files (app, package, package lock)?
i have shared hosting, but i am coming from a PHP and Python back ground. i can see node js app setup here on my shared server. read three books cover to cover, struggled with this for 3 years, you sorted me out in less than 5 minutes. you have absolutely no idea how grateful and happy i am right now. thank you so much bro. I owe you big. biiiiiig simba big. :D
did the freecodecamp courses and aced everything, this is the only part where i was seeing pitch blackness. thank you so much.
Well explained. Thank you ❣❣
Thank you from Brazil.
Thanks for this!
Hello. Thanks for useful information. This is best tutorual for me. I didn't know it was running Apache Server Node.
Thanks It is working
In new Cpanel version when creatinf subdomains we have to use Domains instead, subdomains have been deprecated, but once i want to make new subdomain it automatically places it under public_html. Can you please make a new video on updated Cpanel?
Well explained, Thank you
You're welcome!
@@OpenJavaScript Hi, how can we set up staging environment here
One could also serve the Node app via pm2 or forever. That could take care of the directory listing vulnerability.
thank you for this video
Hi, In my nodes application I have used Nuxt.js and deployed in Cpanel but I am getting 503 issue. Should I reinstall node_modules?
Thank you😊
Hi sir, I'm uploading a Nextjs 13 to cPanel, I see that on the select node version just appears 14.x while my app is using 16.x version? Does it work well? I tried to upload with version 14.x on cPanel but its not working and I get an error some packages not compatible with npm and node version
Is there any extra activities related to deployed the node js web application
Thank you so much;
You are welcome!
Thank you
I made a website using html,css, javascript for frontend and express nodejs for my backend and my storage using mongodb and store in AWS and run in local host,but I want to deploy my website so can you please help me how to upload and also how to add domain for my website
Hello, im trying to deploy my Node Project over the C Panel however when Installing the dependencies, the Npm takes forever and causes error later on. Could uou help me with that?
To get this to work did you paid for a VPS plan or just a regular Hosting plan?
Hi sir
Can you please share how can we host nodejs project in iis with static url, kindly help me sir
Nodejs is it supported to business web hosting plan of the Hosting
Thanks
its only basic , i am stuck on deploying it on shared hosting, running server and displaying message is not issue , i want my all routes worked perfectly . It only showing server is running , when I opened my site!!
can you do CI/CD version
Where you have hosted,
Hostinger, Hostgator or any other platform
thanks
for me it's 503 error coming, what to do?
Is it okey if i have react client part of website in one folder, Nodejs server in second folder, mysql as third folder and all three of those folders to be inside one root folder for all of them to be deployed to Cpanel?
Ideally, these should be in separate locations: frontend in the public_html folder, Node.js app usually in its own folder in the root folder and you can access your MySQL database(s) via phpMyAdmin in cPanel.
You could try this but I wouldn't recommend it for security (potentially making sensitive data more accessbile) and also compatibility (cPanel is usually set up to expect MySQL to be stored in a separate location).
But, the good news is, all three can interact with each other when dpeloyed. So you could make a request from your React app to a Node.js server that then contacts your MySQL database.
For how to interact with a MySQL server in Node.js, I cover that in this tutorial: ruclips.net/video/xwfeik3bPpw/видео.html
If you have any questions about it, let me know in the comments on that video.
i dont have a subdomain tool on my cpanel, but i have everything else, what to do, please help
very good
Thanks!
omg no indian accent thanks to you ^^
thankyou
You're welcome!
Thank you for this video, i just subscribe to your channel, Can i access my cpanel outside namecheap?
You can only access your cpanel with your hosting provider but you might also be able to connect to your shared hosting space via SSH (if you provider supports it).
If 'terminal' is available in your cpanel, it means you probably have access and can do it. Otherwise you should contact your host. They may even provide documentation!
How do I create a storage database in Cpanel and be able to access it in the NodeJs website?
I did just post a video on this very topic: ruclips.net/video/xwfeik3bPpw/видео.html
If you have any questions, let me know in the comments.
i try to run npm index.js but it say "permission denied". Can anyone help?
MongoClient mongoose not supported?
thank
This is for a subdomain. That is such a boundary condition - few people would ever want this. People want to create an app for their domain, or on shared hosting with another one of their domains.
What about if we want to host the app on a main domain...not subdomain. how do we do that?
First thing I would try is setting the Application URL ( around 3:50 in the video ) to the main domain when setting up a new Node app.
If this doesn't work, it's likely that there is a conflict between your hosting service being set up to serve files from your public_html folder and your attempt to serve a Node.js app on that domain. In this case I'd contact your web host to let them know you'd like your hosting configured to serve your Node app on the main doamin.
Can you show process of editing code of nextjs or adding new file after deployment
If you make changes to your app itself and want these to be effective, you need to redeploy it.
The simplest way would be to stop your app, update the files in the files folder (application root path) and then start the app again.
If you just change the files if the application root path without redeploying, these won't be effective.
@@OpenJavaScript but we have to run "npm run build" command so that application get ready for deployment then how to do that.
I tried but it's not working.
@@OpenJavaScript can you make video on it for nextjs app.
@@vishalrahangdale3624 That's a good idea for a tutorial, which I will make soon
For now, try this:
Creare the following server.js file in your project (code from Next.js website):
// server.js
const { createServer } = require('http')
const { parse } = require('url')
const next = require('next')
const dev = process.env.NODE_ENV !== 'production'
const hostname = 'localhost'
const port = 3000
// when using middleware `hostname` and `port` must be provided below
const app = next({ dev, hostname, port })
const handle = app.getRequestHandler()
app.prepare().then(() => {
createServer(async (req, res) => {
try {
// Be sure to pass `true` as the second argument to `url.parse`.
// This tells it to parse the query portion of the URL.
const parsedUrl = parse(req.url, true)
const { pathname, query } = parsedUrl
if (pathname === '/a') {
await app.render(req, res, '/a', query)
} else if (pathname === '/b') {
await app.render(req, res, '/b', query)
} else {
await handle(req, res, parsedUrl)
}
} catch (err) {
console.error('Error occurred handling', req.url, err)
res.statusCode = 500
res.end('internal server error')
}
})
.once('error', (err) => {
console.error(err)
process.exit(1)
})
.listen(port, () => {
console.log(`> Ready on ${hostname}:${port}`)
})
})
Then change the script section in your package.json file to this:
"scripts": {
"dev": "node server.js",
"build": "next build",
"start": "NODE_ENV=production node server.js"
}
After this, run 'npm run build' locally and then upload the resulting files to the 'application root' folder you specify in cPanel and set the 'application startup file' also in cPanel to server.js.
Then, deploy your app as per this tutorial and it should hopefully be working.
When node app was not running the whole file where listed and anyone can view this, does this mean if our app is crashed and anyone enter then he will be able to see our backend files ???
If yes then it will be a Big issue if not then how we be sure that our backend file is secured
Good question!
There are actually a few ways of doing that:
1) Set the "application root" to a folder that is not the same as the main folder for the domain you are running the app on. Then, if the app crashes, the folder doesn't contain the app files.
2) Use a full stop in front of any files that are in the domain folder you don't want to server (e.g. ".app.js"). Though this can be error-prone.
3) Change the folder permissions so that the folder cannot be read (can be done in cPanel file manager).
Probably 1 and 3 are the most secure solutions.
3:38 Hello my friend, which server are you using? I have Hostgator VPS. I don't have the option to (setup node.js app) app in my cpanel.
have you done setup, tried SSH?
I LOVE YOU "CABRON" JEJEJE
does someone by any chance know how to use cpanel with a newer version of node i need atleast 16?
The hosting provider I am using in this video (HostWithLove: bit.ly/3V2RM9Q) now allows you to run apps in Node 18.14 (and also still older versions, if you prefer).
If you already have shared hosting with cPanel, the easiest way would be to contact your hosting provider, asking them to update it on their side.
If you have command line access (not always allowed) and are comfortable with using it (I wouldn't advise this if you are not), you may consider updating yourself.
Agree they made unnecessary changes. I have hard times settting up NodeJS now due to retarded update.
it is so weird that there is no "Setup Node.js App" section in "SOFTWARE". What should i do. I was going to deploy Nextjs
To deploy your Next.js app in the way I did in this tutorial, you need to follow a few preparatory steps.
Someone else asked about this, so I'll copy in the answer again here:
---
Creare the following server.js file in your project (code from Next.js website):
// server.js
const { createServer } = require('http')
const { parse } = require('url')
const next = require('next')
const dev = process.env.NODE_ENV !== 'production'
const hostname = 'localhost'
const port = 3000
// when using middleware `hostname` and `port` must be provided below
const app = next({ dev, hostname, port })
const handle = app.getRequestHandler()
app.prepare().then(() => {
createServer(async (req, res) => {
try {
// Be sure to pass `true` as the second argument to `url.parse`.
// This tells it to parse the query portion of the URL.
const parsedUrl = parse(req.url, true)
const { pathname, query } = parsedUrl
if (pathname === '/a') {
await app.render(req, res, '/a', query)
} else if (pathname === '/b') {
await app.render(req, res, '/b', query)
} else {
await handle(req, res, parsedUrl)
}
} catch (err) {
console.error('Error occurred handling', req.url, err)
res.statusCode = 500
res.end('internal server error')
}
})
.once('error', (err) => {
console.error(err)
process.exit(1)
})
.listen(port, () => {
console.log(`> Ready on ${hostname}:${port}`)
})
})
Then change the script section in your package.json file to this:
"scripts": {
"dev": "node server.js",
"build": "next build",
"start": "NODE_ENV=production node server.js"
}
After this, run 'npm run build' locally and then upload the resulting files to the 'application root' folder you specify in cPanel and set the 'application startup file' also in cPanel to server.js.
Then, deploy your app as per this tutorial and it should hopefully be working.
I know how to setup up my app. The problem is that I don't see the "Setup Nodejs App" button
@@a.anvarbekov Ah, I see. In this case it's most likely that your hosting provider does not support Node.js in cPanel. I'd first contact them to see if the will install it for you.
Otherwise, you might consider a hosting provider that will support Node.js apps. If you do go down that route, you might consider using the one I do in the video, HostWithLove (Node comes installed as standard): bit.ly/3V2RM9Q
@@OpenJavaScript next js 14 required node js 18.7. but in my shared namecheap hosting we have node js 14 only. I am getting an error on the electron pkg. any solution? I would appreciate your help.
What is the nodejs version in local?
You can host a Node app locally by following this tutorial:
ruclips.net/video/hekIHfOil50/видео.html
Plese, where is the filrs (app, package, package lock)?
Plese, where is the files (app, package, package lock)?
It works fine, except for the static files, it doesn't seem to find them, how is it configured?
You are in luck!
I did a tutorial on serving static files recently: ruclips.net/video/fyc-4YmgLu0/видео.html
imagine i had to go pay for a full cloud server coz i couldnt find a way to host the apps i had made for clients which were running fine offline but on shared hosting .... tears. hehehehee
Nodejs version 16 is supported or not...?
Yes, 16 is supported as well as 18 by the host I'm using. I used the default version upon creating a new app in this video but you can select a more recent one.
this is a SECURITY HAZARD, for any newbies out there knowing nothing about hosting, yet get a hosting and come accross your video, do the same, then boom they are at a risk of exposing their whole app
the app shouldnt be host on the same folder as the public files
💙💙
💙
Sir node.js application is not showing to me why?
There's a good chance that Node.js isn't showing in cPanel because it hasn't been installed on your server.
If you have an existing hosting package, you should contact your host and ask them if it is possible to install.
Otherwise, you might consider the host I'm using in this video, HostWithLove, which has packages that come Node.js installed as standard: bit.ly/3V2RM9Q
Presenting an how-to-deploy-an-application-tutorial for beginner which has a MAJOR SECURITY issue is great. NEVER !!! upload your server files inside your main domain name. If your application is offline or your server crashed, ALL SOURCES CODE IS LEAKED and can be freely downloaded just by visiting the domain name.
This makes sense to me so are we supposed to host our server files on a different domain?
Sure. Create of configure a new domain name and store your files in a different folder. If you put your source code inside your domain name, all your files will be leaked as at 3:23
Wouldn't password protection solve this?
@@M3R14M. As far as I know, there is no such option on Cpanel. Just store your files in a different folder than your domain name.
Password protect a crashed server? 😮
How can Cpanel know that the express server is on port 3000?
When creating a new Node application, you specify an application startup file (e.g. app.js) and from this the port number to run the server on is read.
In this example, 'app.listen(process.env.PORT || 3000)' is specified, meaning that when deploying, the server will first look to the value of the PORT environment variable for your suggested port and, if no value is present, use 3000.
But note that, on a shared server via cpanel (unlike locally, where you have full control over your computer as a server), your application may be silently run on a different port from the one you suggest.
@@OpenJavaScript so when a client app calls the server, it automatically redirect the request from the http default port to the 3000?
@EVOLI The server that is hosting and running cPanel makes the final call on which port to run your app. It will configure the Node app running on that port to be served when a request comes in to domain you are choosing to run your app on.
The port you specify is suggested for the hosting server (it may run on the port you suggest or a different one).
@@OpenJavaScript so clear! Thank you!
I'm facing a ssl issue.. I can't download any npm pack from npm commands, issue 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY'. SSL is ok, I did the procedure with autossl. I know I can bypass by setting strict-ssl=false, but the problem shows up again when, in discordjs, I try to connect to my own sql server. Same ssl issue. Any idea how to resolve? I've no more ideas, I'm near desperate -.-
same issue here have you found a solution?
Doesn't work! Am I the only one?
What seems to be the issue?
@@OpenJavaScript RangeError: WebAssembly.instantiate(): Out of memory: wasm memory
at internal/deps/cjs-module-lexer/dist/lexer.js:1:33593
at async initCJSParse (internal/modules/esm/translators.js:72:5)
at async Loader.commonjsStrategy (internal/modules/esm/translators.js:185:18)
@@OpenJavaScript It works without any dependencies, but with express only it dosen't works. is it a problem with the physical memory ? actually i have only 1Go.
Spent 3 days trying node on Cpanel. All kinds of errors!
@@efoobright5041 It's unlikely to be size-related as Express isn't that large relative to your limit.
Because it's working only without dependencies I would guess it's a problem of node_modules being uploaded correctly.
If npm install in cPanel isn't working for you (when the app is stopped), I would recommend trying to upload the node_modules folder to the root directory of your app yourself. I have tried this previously and it fixed a similar issue.
5 minutes !!!!
waste of time to watch