Bobcares

Plesk Nextjs Setup: How to Do it?

by | Jun 29, 2023

Let us learn how to see how to do the plesk nextjs setup with the support of our Plesk hosting support services at Bobcares.

How to set up a Nextjs application on Plesk?

plesk nextjs setup

Following these broad procedures will allow us to host a Next.js application on a Plesk control panel:

  1. Log in to the Plesk Control Panel:

    Log in using the Plesk control panel credentials. Create a domain or subdomain in Plesk that will host the Next.js application. Ensure to correctly set up the domain or subdomain and point it to the Plesk server.

  2. Install Node.js Support:

    Enable Node.js support in Plesk for the domain or subdomain where the Next.js application to host it. This step guarantees that Node.js apps may be executed on the server.

  3. Node.js Configuration:

    Enter the following information in the domain or subdomain’s Node.js settings:

    a: Document Root:

    Set the document root to the folder containing the Next.js application.

    b: Application Mode: Select “Production” mode to execute your Next.js application in production.

    c: Application Root:

    Set the application root to the folder containing your Next.js application.

  4. Enable Proxy Mode:

    Set the domain or subdomain to use proxy mode. This setting is importat for Plesk to route incoming requests to the Next.js application.

  5. Dependencies to Install:

    Run the following command in the folder containing the Next.js application to install the essential dependencies:

    npm install

  6. Create a Next.js application:

    Run the build command to create the Next.js application:

    npm run build

    This command builds and optimizes the Next.js application for deployment in production.

  7. Restart Node.js:

    In Plesk, restart the Node.js service to implement the modifications and confirm that the Next.js application is operational.

At this point, the Next.js application should be hosted and accessible through the Plesk-configured domain or subdomain. Based on the exact requirements, we may establish SSL certificates, DNS settings, and other Plesk capabilities.

Please keep in mind that the specific processes and options will depend on the version of Plesk we are running. For comprehensive instructions unique to the Plesk version, it is advisable to check the Plesk manual or user guides.

[Need assistance with similar queries? We are here to help]

Conclusion

To sum up we have now seen how to do the plesk nextjs setup with the support of our tech support team.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF