# Issue installing Discourse on OVH VPS Ubuntu 22.04
**URL:** https://meta.discourse.org/t/issue-installing-discourse-on-ovh-vps-ubuntu-22-04/256746
**Category:** Self-hosting
**Created:** [March 2, 2023, 12:03am UTC](https://meta.discourse.org/t/issue-installing-discourse-on-ovh-vps-ubuntu-22-04/256746 "2023-03-02T00:03:33Z")
**Posts on this page:** 11
**Page:** 3
### Author:  [@ClawdiaWolf](https://meta.discourse.org/u/ClawdiaWolf)
#### Post date: [March 3, 2023, 3:40pm UTC](https://meta.discourse.org/t/issue-installing-discourse-on-ovh-vps-ubuntu-22-04/256746/42 "2023-03-03T15:40:06Z")
> [@Jagster](#):
>
> Easier task is to do `systemctl status nginx`. If the status is alive then you stop it `systemctl stop nginx` and to be sure it will stay taht way you will do `systemctl disable nginx`.
Only true if it’s being managed by systemd, which isn’t always the case. I’ve seen too many instances where some random package installs it, disables the service, and then starts and stops it as needed.
I’ve also seen at least one package in the past that installed a .service file for it even though nginx wasn’t actually installed.
The both of those will happily tell you the status is disabled. The apt method guarantees that if it is actually installed you’ll know unless it was compiled from source, and we probably wouldn’t be having this conversation if that was the case. 🙂
---
### Author:  [@Titi](https://meta.discourse.org/u/Titi)
#### Post date: [March 3, 2023, 8:13pm UTC](https://meta.discourse.org/t/issue-installing-discourse-on-ovh-vps-ubuntu-22-04/256746/43 "2023-03-03T20:13:08Z")
Hello @Claudia Thanks for your help.
The result is
```plaintext
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
elpa-nginx-mode/jammy 1.1.9-2 all
golang-github-nginxinc-nginx-plus-go-client-dev/jammy 0.9.0-2 all
kopano-webapp-nginx/jammy 3.5.14+dfsg1.orig-1 all
libnginx-mod-http-auth-pam/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-http-cache-purge/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-http-dav-ext/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-http-echo/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-http-fancyindex/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-http-geoip2/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-http-geoip/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-http-headers-more-filter/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-http-image-filter/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-http-ndk/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-http-perl/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-http-subs-filter/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-http-uploadprogress/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-http-upstream-fair/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-http-xslt-filter/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-mail/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-nchan/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-rtmp/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-stream-geoip2/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-stream-geoip/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
libnginx-mod-stream/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
lua-nginx-cookie/jammy 0.1.0-1.1 all
lua-nginx-dns/jammy 0.20-1 all
lua-nginx-kafka/jammy 0.07-1 all
lua-nginx-memcached/jammy 0.14-1.1 all
lua-nginx-redis-connector/jammy 0.06-1 all
lua-nginx-redis/jammy 0.27-1.1 all
lua-nginx-string/jammy 0.11-1 all
lua-nginx-websocket/jammy 0.08-1 all
nginx-common/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 all
nginx-confgen/jammy 2.0-1 amd64
nginx-core/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
nginx-doc/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 all
nginx-extras/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
nginx-full/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
nginx-light/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
nginx/jammy-updates,jammy-security 1.18.0-6ubuntu14.3 amd64
prometheus-nginx-exporter/jammy 0.10.0-1 amd64
python3-certbot-nginx/jammy 1.21.0-1 all
```
---
### Author:  [@Titi](https://meta.discourse.org/u/Titi)
#### Post date: [March 3, 2023, 8:15pm UTC](https://meta.discourse.org/t/issue-installing-discourse-on-ovh-vps-ubuntu-22-04/256746/44 "2023-03-03T20:15:54Z")
Hello @Jagster
When I do systemctl status ngin
The result is : Unit nginx.service could not be found.
---
### Author:  [@ClawdiaWolf](https://meta.discourse.org/u/ClawdiaWolf)
#### Post date: [March 3, 2023, 8:44pm UTC](https://meta.discourse.org/t/issue-installing-discourse-on-ovh-vps-ubuntu-22-04/256746/45 "2023-03-03T20:44:38Z")
You’ve definitely got the full nginx installed. I also see some web applications listed that require it, like Kopano.
Does someone else have access to your VPS?
---
### Author:  [@Titi](https://meta.discourse.org/u/Titi)
#### Post date: [March 3, 2023, 8:46pm UTC](https://meta.discourse.org/t/issue-installing-discourse-on-ovh-vps-ubuntu-22-04/256746/46 "2023-03-03T20:46:47Z")
@xiaokong23357 I did this in app.yml file
expose:
- “80:80” # http
- “9090:80” # http" ensures that nginx can be proxed to discourse
- “443:443” # https
After I did ./launcher rebuild app
Always the same message on the browser :
# Welcome to nginx!
If you see this page, the nginx web server is successfully installed and working. Further configuration is required.
For online documentation and support please refer to [nginx.org](http://nginx.org/).
Commercial support is available at [nginx.com](http://nginx.com/).
_Thank you for using nginx._
---
### Author:  [@Titi](https://meta.discourse.org/u/Titi)
#### Post date: [March 3, 2023, 8:48pm UTC](https://meta.discourse.org/t/issue-installing-discourse-on-ovh-vps-ubuntu-22-04/256746/47 "2023-03-03T20:48:53Z")
@Claudia
No only me and the provider OVH of the VPS
---
### Author:  [@Titi](https://meta.discourse.org/u/Titi)
#### Post date: [March 3, 2023, 8:50pm UTC](https://meta.discourse.org/t/issue-installing-discourse-on-ovh-vps-ubuntu-22-04/256746/48 "2023-03-03T20:50:26Z")
> [@Titi](#):
>
> When I do systemctl status ngin
> The result is : Unit nginx.service could not be found.
If I’ve a full ngix installed why when I do systemctl status ngin
The result is : Unit nginx.service could not be found.
Or it’s installed but not running.
---
### Author:  [@xiaokong23357](https://meta.discourse.org/u/xiaokong23357)
#### Post date: [March 4, 2023, 1:42am UTC](https://meta.discourse.org/t/issue-installing-discourse-on-ovh-vps-ubuntu-22-04/256746/49 "2023-03-04T01:42:06Z")
You can delete port 80 without using it to prevent conflicts between discourse and nginx
---
### Author:  [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [March 4, 2023, 7:54am UTC](https://meta.discourse.org/t/issue-installing-discourse-on-ovh-vps-ubuntu-22-04/256746/50 "2023-03-04T07:54:59Z")
> [@Titi](#):
>
> ”9090:80” # http" ensures that nginx can be proxed to discourse
You don’t have Nginx working as reverse proxy. Plus now you are redirecting two ports as 80. You must have either one, not both. And because you aren’t using Nginx, and because of that you don’t have virtual host proxying to port 9090 or any other port you must comment out that.
Do you have anything else installed via docker? Because now it sounds a bit like your Nginx in docker works but Discourse itself is down.
That was a fresh install, right? I would discard whole VPS and start over.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 5, 2023, 12:08am UTC](https://meta.discourse.org/t/issue-installing-discourse-on-ovh-vps-ubuntu-22-04/256746/51 "2023-03-05T00:08:21Z")
I would spin up a new vm and start over, but in any case, you can try to remove nginx.
```plaintext
apt remove nginx
```
You need to leave discourse with access to port 80.
It is a good bet that you have hit let’s encrypt rate limits. You’ll likely need to use a different subdomain or wait a week.
---
### Author:  [@Titi](https://meta.discourse.org/u/Titi)
#### Post date: [March 9, 2023, 11:01am UTC](https://meta.discourse.org/t/issue-installing-discourse-on-ovh-vps-ubuntu-22-04/256746/52 "2023-03-09T11:01:21Z")
Hello
I didn’t find the solution so I decided to change hosting provider.
Thanks to all for the support.
[Previous page](https://meta.discourse.org/t/issue-installing-discourse-on-ovh-vps-ubuntu-22-04/256746.md?page=2)