# Transition problem
**URL:** https://meta.discourse.org/t/transition-problem/292282
**Category:** Self-hosting
**Tags:** unsupported-install
**Created:** [January 19, 2024, 7:32pm UTC](https://meta.discourse.org/t/transition-problem/292282 "2024-01-19T19:32:41Z")
**Posts on this page:** 18
**Page:** 1
### Author:  [@Scart](https://meta.discourse.org/u/Scart)
#### Post date: [January 19, 2024, 7:32pm UTC](https://meta.discourse.org/t/transition-problem/292282/1 "2024-01-19T19:32:42Z")
I was installing forum on a remote server, then added my main site to the server via CPanel for remote servers so moved from regular NameCheap hosting to a remote server, then I got the forum site down and I can’t even run the `./launcher rebuild app` command or uninstall. It writes an error that there is no file `*.yml` or can not access, by checking ls -al does not find a file with app.yml or another name and says that the ports are not open.
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [January 19, 2024, 7:40pm UTC](https://meta.discourse.org/t/transition-problem/292282/2 "2024-01-19T19:40:37Z")
I don’t believe CPanel is supported.
> [@Installing Discourse on a cPanel Server](https://meta.discourse.org/t/installing-discourse-on-a-cpanel-server/91648/3):
>
> I think that Docker on CentOS 6 may be challenging. If you can install Docker and make it work, you’ll be getting closer. You’ll also need to figure out how to reverse proxy whatever is the front door (Apache?) to Discourse. Something like [How to set up Discourse on a server with existing Apache sites](https://meta.discourse.org/t/how-to-set-up-discourse-on-a-server-with-existing-apache-sites/30013) For $5/month, you can avoid a bunch of pain.
> [@Can Discourse work on a Server beside cPanel?](https://meta.discourse.org/t/can-discourse-work-on-a-server-beside-cpanel/93323/2):
>
> Short Answer: No, You can’t Long answer: You can search this forum and find people complaining about their install attempts either failing instantly or failing at a later date. Both, apache2 and CentOS are not good choice of running discourse with. I wouldn’t say it won’t work, but, it won’t work out of the box and would require a good understanding of discourse, cpanel, apache2 and proxies. Plus, it will require some thought to how you plan on restoring/preserving the configuration in case c…
---
### Author:  [@Scart](https://meta.discourse.org/u/Scart)
#### Post date: [January 19, 2024, 7:42pm UTC](https://meta.discourse.org/t/transition-problem/292282/3 "2024-01-19T19:42:48Z")
Well, they should work on the same server, and not conflict I now on that domain name simply: Index of /
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [January 19, 2024, 7:43pm UTC](https://meta.discourse.org/t/transition-problem/292282/4 "2024-01-19T19:43:21Z")
Good Luck!
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 19, 2024, 8:59pm UTC](https://meta.discourse.org/t/transition-problem/292282/5 "2024-01-19T20:59:11Z")
I think that cPanel only works for PHP-based stuff. If it had a reverse proxy, you might be able to make it work, but it would be hard. If it did have a reverse proxy and you knew a lot about how it worked, you could install Discourse on its own server, see how that worked, then change the ports in the `app.yml` file to whatever the reverse proxy would point to and then you could conceivably copy that app.yml to the cPanel server and then it might work.
But if all of that doesn’t make complete sense, you’ll be better of just sticking with installing Discourse on its own server with a [standard install](https://meta.discourse.org/t/142537?silent=true).
---
### Author:  [@Scart](https://meta.discourse.org/u/Scart)
#### Post date: [January 20, 2024, 10:11pm UTC](https://meta.discourse.org/t/transition-problem/292282/6 "2024-01-20T22:11:35Z")
okay, i buy another VPS Server
OC: Ubuntu-20.04-amd64
RAM: 2 GB
Port speed: 250 Mbps
Disk space: 20 GBand it says this, I need to increase the RAM?
```plaintext
WARNING: Discourse requires at least 2GB of swap when running with 2GB of RAM
or less. This system does not appear to have sufficient swap space.
Without sufficient swap space, your site may not work properly, and future
upgrades of Discourse may not complete successfully.
Ctrl+C to exit or wait 5 seconds to have a 2GB swapfile created.
install: cannot remove '/swapfile': Operation not permitted
fallocate: fallocate failed: Text file busy
mkswap: error: /swapfile is mounted; will not make swapspace
swapon: /swapfile: swapon failed: Device or resource busy
/swapfile swap swap auto 0 0
vm.swappiness = 10
Failed to create swap: are you root? Are you running on real hardware, or a fully virtualized server?
```
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 20, 2024, 11:45pm UTC](https://meta.discourse.org/t/transition-problem/292282/7 "2024-01-20T23:45:43Z")
20 gb if disk space is likely to be too little.
The error says that it failed roku at up swap space. Are you running as root?
It would appear that you don’t have rights to create swap for some reason. Either you’re not running as user root, or you don’t have a proper vm that gives you the control you need.
---
### Author:  [@Scart](https://meta.discourse.org/u/Scart)
#### Post date: [January 21, 2024, 1:55pm UTC](https://meta.discourse.org/t/transition-problem/292282/8 "2024-01-21T13:55:33Z")
- 2 CPU cores
- 2 GB RAM
- 40 GB SSD RAID 10
- 1000 GB bandwidth
it’s nice VPS server?
---
### Author:  [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [January 21, 2024, 2:13pm UTC](https://meta.discourse.org/t/transition-problem/292282/9 "2024-01-21T14:13:01Z")
> [@Scart](#):
>
> 2 GB RAM
This is the bare minimum now imho. Better to have 4GB. Even with 2GB swap, online updates with only 2 + 2 are painful!
You also need to have Ubuntu 22.x as there are recent new dependencies on this.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 21, 2024, 3:14pm UTC](https://meta.discourse.org/t/transition-problem/292282/10 "2024-01-21T15:14:59Z")
Are you running as root?
Can you run docker?
---
### Author:  [@Scart](https://meta.discourse.org/u/Scart)
#### Post date: [January 21, 2024, 3:32pm UTC](https://meta.discourse.org/t/transition-problem/292282/11 "2024-01-21T15:32:49Z")
i buy
- **CPU** 4 Cores
- **RAM** 6 GB
- **Disk Space** 120 GB SSD RAID 10
and i install docker, git, clone repository and i run a `./discourse-setup` and I get the following
```plaintext
Checking your domain name . . .
WARNING: Port 443 of computer does not appear to be accessible using hostname: forum.layerzero.news.
WARNING: Connection to http://forum.layerzero.news (port 80) also fails.
This suggests that forum.layerzero.news resolves to some IP address that does not reach this
machine where you are installing discourse.
The first thing to do is confirm that forum.layerzero.news resolves to the IP address of this server.
You usually do this at the same place you purchased the domain.
If you are sure that the IP address resolves correctly, it could be a firewall issue.
A web search for "open ports YOUR CLOUD SERVICE" might help.
This tool is designed only for the most standard installations. If you cannot resolve
the issue above, you will need to edit containers/app.yml yourself and then type
./launcher rebuild app
```
How do I fix it because I can’t even delete it all from another VPS or what can I do?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 21, 2024, 3:51pm UTC](https://meta.discourse.org/t/transition-problem/292282/12 "2024-01-21T15:51:42Z")
> [@Scart](#):
>
> `forum.layerzero.news`
If you ssh to that host name, so you get to the correct vm?
---
### Author:  [@Scart](https://meta.discourse.org/u/Scart)
#### Post date: [January 21, 2024, 4:12pm UTC](https://meta.discourse.org/t/transition-problem/292282/13 "2024-01-21T16:12:00Z")
well I’m completely connected to the new vm, I already had discourse on this subdomain.
if I’m looking at it right.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 21, 2024, 4:15pm UTC](https://meta.discourse.org/t/transition-problem/292282/14 "2024-01-21T16:15:30Z")
The name must resolve to your vm ip address.
```plaintext
$ dig +short forum.layerzero.news
91.208.127.60
```
Is the new vm 91.208.127.60?
---
### Author:  [@Scart](https://meta.discourse.org/u/Scart)
#### Post date: [January 21, 2024, 4:28pm UTC](https://meta.discourse.org/t/transition-problem/292282/15 "2024-01-21T16:28:20Z")
> [@pfaffman](#):
>
> The
no my new server 162.254.32.63
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 21, 2024, 5:04pm UTC](https://meta.discourse.org/t/transition-problem/292282/16 "2024-01-21T17:04:38Z")
You need to update the dns so that it points to the new server.
That’s what this was trying to tell you
> [@Scart](#):
>
> `This suggests that forum.layerzero.news resolves to some IP address that does not reach this machine where you are installing discourse. `
---
### Author:  [@Scart](https://meta.discourse.org/u/Scart)
#### Post date: [January 21, 2024, 6:18pm UTC](https://meta.discourse.org/t/transition-problem/292282/17 "2024-01-21T18:18:25Z")
> [@pfaffman](#):
>
> ```plaintext
> $ dig +short forum.layerzero.news
> 91.208.127.60
>
> ```
```plaintext
$ dig +short forum.layerzero.news
162.254.32.63
```
it’s command that I update the ip or should I update the ip in my domain service?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [January 21, 2024, 6:33pm UTC](https://meta.discourse.org/t/transition-problem/292282/18 "2024-01-21T18:33:32Z")
That’s how to check. You need to update it at wherever the dns is. (name cheap, perhaps)
DNS is always the problem.