[{"data":1,"prerenderedAt":31},["ShallowReactive",2],{"doc-en-host-ruby-application-plesk":3},{"path":4,"slug":5,"title":6,"description":7,"category":8,"subcategory":9,"icon":10,"date":11,"author":12,"order":13,"image":14,"tags":15,"keywords":21,"docGroup":28,"docGroupIcon":28,"link_fr":29,"bodyHtml":30},"\u002Fdocs\u002Fen\u002Fcloud\u002Fhebergement-web\u002Fhost-ruby-application-plesk","host-ruby-application-plesk","How to Host a Ruby Application on Plesk","Host a Rack-based Ruby application on Winheberg Plesk web hosting, folder layout, public root, enabling Ruby, gem installation, restart and troubleshooting.","cloud","hebergement-web","tabler:file-text","2026-11-02","Winheberg",153,"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-ruby-application-plesk.webp",[16,17,18,19,20],"Ruby","Plesk","Rack","Passenger","Web Hosting",[22,23,24,25,26,27],"host ruby","ruby plesk","rack application","plesk passenger","bundle install","sinatra hosting","","\u002Fdocs\u002Fhebergement-web\u002Fheberger-application-ruby-plesk","\u003Ch2>Context\u003C\u002Fh2>\n\u003Cp>Your \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fcloud\u002Fweb-hosting\">Winheberg web hosting\u003C\u002Fa> can run Rack-based Ruby applications, such as those written with Sinatra, Roda or Hanami. Plesk serves them with Phusion Passenger, which starts your application on the first visit and keeps it in memory.\u003C\u002Fp>\n\u003Cp>The Plesk Ruby extension handles the Ruby version, the installation of the gems listed in your \u003Ccode>Gemfile\u003C\u002Fcode> and the application restart. You need no command-line access.\u003C\u002Fp>\n\u003Cp>This guide covers the expected folder layout, the website root setting, enabling Ruby, installing gems and the most common errors.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The Winheberg Plesk panel is displayed in French. Menu, field and button names are quoted below exactly as they appear on screen, followed by their English meaning.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>Prerequisites\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>A Winheberg web hosting plan with access to the Plesk panel\u003C\u002Fli>\n\u003Cli>A domain or subdomain dedicated to the application, see our guide \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Fconnect-external-domain-plesk\">How to Connect an External Domain to Your Plesk Hosting\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Your application, with its \u003Ccode>config.ru\u003C\u002Fcode> file and its \u003Ccode>Gemfile\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>An application that needs to run command-line tasks, such as Ruby on Rails migrations, requires SSH access. If your plan does not open it, a \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fvps\">Winheberg VPS\u003C\u002Fa> gives you full control of the server.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>1. Prepare the application layout\u003C\u002Fh2>\n\u003Cp>Plesk expects a specific layout. The application folder holds \u003Ccode>config.ru\u003C\u002Fcode> and the \u003Ccode>Gemfile\u003C\u002Fcode>, and a \u003Ccode>public\u003C\u002Fcode> subfolder receives static files such as images or stylesheets.\u003C\u002Fp>\n\u003Cdiv class=\"md-table md-table--info md-table--striped\">\u003Cdiv class=\"md-table__caption\">Expected layout\u003C\u002Fdiv>\u003Cdiv class=\"md-table__scroll\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Item\u003C\u002Fth>\n\u003Cth>Location\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Application folder\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>app.example.com\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Startup file\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>app.example.com\u002Fconfig.ru\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Gem list\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>app.example.com\u002FGemfile\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Static files\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>app.example.com\u002Fpublic\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003C\u002Fdiv>\u003Cdiv class=\"md-table__footer\">Example for an app.example.com subdomain, whose folder has the same name.\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cp>To test the hosting before uploading your real application, here is a minimal application. The \u003Ccode>config.ru\u003C\u002Fcode> file holds the application itself.\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-ruby\">run lambda { |env|\n  [200, { &quot;content-type&quot; =&gt; &quot;text\u002Fhtml; charset=utf-8&quot; }, [&quot;&lt;h1&gt;Bonjour depuis Ruby #{RUBY_VERSION}&lt;\u002Fh1&gt;&quot;]]\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The \u003Ccode>Gemfile\u003C\u002Fcode> declares the \u003Ccode>rack\u003C\u002Fcode> gem it needs.\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-ruby\">source &quot;https:\u002F\u002Frubygems.org&quot;\n\ngem &quot;rack&quot;\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Upload these files to the application folder with the Plesk \u003Cstrong>Fichiers\u003C\u002Fstrong> (\u003Cem>Files\u003C\u002Fem>) manager, or with our guide \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Fconnect-ftp-filezilla-plesk\">How to Connect to Your Plesk Hosting over FTP with FileZilla\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch2>2. Point the website to the public folder\u003C\u002Fh2>\n\u003Cp>Open your domain from \u003Cstrong>Sites Web &amp; Domaines\u003C\u002Fstrong> (\u003Cem>Websites &amp; Domains\u003C\u002Fem>), then the \u003Cstrong>Hébergement et DNS\u003C\u002Fstrong> (\u003Cem>Hosting &amp; DNS\u003C\u002Fem>) tab and the \u003Cstrong>Hébergement\u003C\u002Fstrong> (\u003Cem>Hosting\u003C\u002Fem>) entry. In \u003Cstrong>Racine du document\u003C\u002Fstrong> (\u003Cem>Document root\u003C\u002Fem>), add \u003Ccode>\u002Fpublic\u003C\u002Fcode> to the application folder path, then click \u003Cstrong>Enregistrer\u003C\u002Fstrong> (\u003Cem>Save\u003C\u002Fem>).\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-ruby-application-plesk-1793618124181-8006fe467e76d8a810cb391a.webp\" alt=\"Document root set to the public folder in the Plesk Hosting Settings\" width=\"615\" \u002F>\n\n\u003Cdiv class=\"markdown-alert markdown-alert-warning\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Cpath d=\"M10.29 3.86L1.82 18a2 2 0 0 0 1.71 3h16.94a2 2 0 0 0 1.71-3L13.71 3.86a2 2 0 0 0-3.42 0z\"\u002F>\u003Cline x1=\"12\" y1=\"9\" x2=\"12\" y2=\"13\"\u002F>\u003Cline x1=\"12\" y1=\"17\" x2=\"12.01\" y2=\"17\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>Plesk then creates the \u003Ccode>public\u003C\u002Fcode> folder if it does not exist, with its default \u003Ccode>index.html\u003C\u002Fcode> page. Delete this file from the \u003Cstrong>Fichiers\u003C\u002Fstrong> manager, otherwise it is what shows at your website address instead of your application.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>3. Enable Ruby\u003C\u002Fh2>\n\u003Cp>In the domain \u003Cstrong>Démarrer\u003C\u002Fstrong> (\u003Cem>Get Started\u003C\u002Fem>) tab, click \u003Cstrong>Ruby\u003C\u002Fstrong>, then \u003Cstrong>Activer Ruby\u003C\u002Fstrong> (\u003Cem>Enable Ruby\u003C\u002Fem>).\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-ruby-application-plesk-1793617797984-d5874d1d15fadbe054572ba9.webp\" alt=\"Get Started tab of a Plesk domain with the Ruby entry\" width=\"800\" \u002F>\n\n\u003Cp>The Ruby page then shows the application settings and its action buttons.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-ruby-application-plesk-1793618123859-427210797d3038ce7db989d1.webp\" alt=\"Ruby page of a domain in Plesk with Bundle install and Restart App\" width=\"800\" \u002F>\n\n\u003Cdiv class=\"md-table md-table--info md-table--striped\">\u003Cdiv class=\"md-table__caption\">Ruby page settings\u003C\u002Fdiv>\u003Cdiv class=\"md-table__scroll\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Setting\u003C\u002Fth>\n\u003Cth>What it shows\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Version de Ruby (\u003Cem>Ruby version\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The version used by the application, which you can change by clicking it\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Mode d&#39;application (\u003Cem>Application mode\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>production\u003C\u002Fstrong>, the mode to keep for a live website\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Root d&#39;application (\u003Cem>Application root\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The application folder, always the parent folder of the website root\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Variables d&#39;environnement personnalisées (\u003Cem>Custom environment variables\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>The variables passed to the application, set with \u003Cstrong>préciser\u003C\u002Fstrong> (\u003Cem>specify\u003C\u002Fem>)\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Type d&#39;app Ruby (\u003Cem>Ruby app type\u003C\u002Fem>)\u003C\u002Ftd>\n\u003Ctd>\u003Cstrong>Basé sur Rack\u003C\u002Fstrong> (\u003Cem>Rack-based\u003C\u002Fem>), detected from the \u003Ccode>config.ru\u003C\u002Fcode> file\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Cp>Check that \u003Cstrong>Root d&#39;application\u003C\u002Fstrong> shows your application folder, for instance \u003Ccode>\u002Fapp.example.com\u003C\u002Fcode>. If it shows \u003Ccode>\u002F\u003C\u002Fcode>, the website root was not set to the \u003Ccode>public\u003C\u002Fcode> folder, go back to step 2.\u003C\u002Fp>\n\u003Ch2>4. Install the gems\u003C\u002Fh2>\n\u003Cp>Click \u003Cstrong>Installation de bundle\u003C\u002Fstrong> (\u003Cem>Bundle install\u003C\u002Fem>). Plesk reads your \u003Ccode>Gemfile\u003C\u002Fcode>, installs the gems in the application \u003Ccode>vendor\u003C\u002Fcode> folder and creates the \u003Ccode>Gemfile.lock\u003C\u002Fcode> file.\u003C\u002Fp>\n\u003Cp>Run \u003Cstrong>Installation de bundle\u003C\u002Fstrong> again after every change to the \u003Ccode>Gemfile\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch2>5. Restart and test the application\u003C\u002Fh2>\n\u003Cp>Click \u003Cstrong>Redémarrer l&#39;app\u003C\u002Fstrong> (\u003Cem>Restart App\u003C\u002Fem>), then open your domain in a browser. The minimal application shows the Ruby version in use.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fhebergement-web\u002Fhost-ruby-application-plesk-1793618124465-922adb9ef4260a9982b42353.webp\" alt=\"Bonjour depuis Ruby page shown by the test application\" width=\"420\" \u002F>\n\n\u003Cp>Remember to \u003Cstrong>Redémarrer l&#39;app\u003C\u002Fstrong> after every upload of a new version of your code, otherwise Passenger keeps the old one in memory.\u003C\u002Fp>\n\u003Ch2>Troubleshooting\u003C\u002Fh2>\n\u003Ch3>❌ The Ruby page says &quot;Fichier de démarrage \u002Fconfig.ru introuvable&quot;\u003C\u002Fh3>\n\u003Cp>Plesk looks for \u003Ccode>config.ru\u003C\u002Fcode> (\u003Cem>startup file not found\u003C\u002Fem>) in the parent folder of the website root, and does not find it there.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Check that the \u003Cstrong>Racine du document\u003C\u002Fstrong> ends with \u003Ccode>\u002Fpublic\u003C\u002Fcode>, as in step 2\u003C\u002Fli>\n\u003Cli>Check that \u003Ccode>config.ru\u003C\u002Fcode> sits in the application folder, not in \u003Ccode>public\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Reload the Ruby page, \u003Cstrong>Root d&#39;application\u003C\u002Fstrong> should show the application folder\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ The default Plesk page shows instead of the application\u003C\u002Fh3>\n\u003Cp>Passenger first serves the files present in \u003Ccode>public\u003C\u002Fcode>, including the default page created by Plesk.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Delete \u003Ccode>public\u002Findex.html\u003C\u002Fcode> from the \u003Cstrong>Fichiers\u003C\u002Fstrong> manager\u003C\u002Fli>\n\u003Cli>Reload your website without cache with Ctrl+F5\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ The application returns an error after an update\u003C\u002Fh3>\n\u003Cp>A gem is missing or the application kept the old version in memory.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Run \u003Cstrong>Installation de bundle\u003C\u002Fstrong> again, then \u003Cstrong>Redémarrer l&#39;app\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Open the \u003Cstrong>Logs\u003C\u002Fstrong> button of the Ruby page to read the error message\u003C\u002Fli>\n\u003Cli>If a gem fails to compile during installation, open a ticket with our support and attach the message\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Best practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>Keep the \u003Cstrong>production\u003C\u002Fstrong> mode for the public website\u003C\u002Fli>\n\u003Cli>Store your keys and passwords in the \u003Cstrong>Variables d&#39;environnement personnalisées\u003C\u002Fstrong>, never in the code\u003C\u002Fli>\n\u003Cli>Commit the \u003Ccode>Gemfile.lock\u003C\u002Fcode> file, it ensures the same gem versions locally and on the hosting\u003C\u002Fli>\n\u003Cli>Only put static files in \u003Ccode>public\u003C\u002Fcode>, the rest of the application must not be reachable from the web\u003C\u002Fli>\n\u003Cli>Turn on HTTPS with our guide \u003Ca href=\"https:\u002F\u002Fwinheberg.com\u002Fen\u002Fdocs\u002Fhebergement-web\u002Flets-encrypt-ssl-certificate-plesk\">How to Generate a Let&#39;s Encrypt SSL Certificate for Your Website\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Need help?\u003C\u002Fh2>\n\u003Cp>If your application still does not start, open a ticket with our support from your \u003Ca href=\"https:\u002F\u002Fbilling.winheberg.com\">client area\u003C\u002Fa>, \u003Cstrong>Technical\u003C\u002Fstrong> department, filling in the \u003Cstrong>Related Product\u003C\u002Fstrong> field with the web hosting concerned. Attach the content of the \u003Cstrong>Logs\u003C\u002Fstrong> of the Ruby page and the Ruby version in use.\u003C\u002Fp>\n\u003Cp>Your Ruby application runs on your hosting, without a single command line 💎\u003C\u002Fp>\n",1794526350772]