Difficulties with digital ocean and aapanel, help please

Zakch93

Elite Member
Joined
Mar 7, 2020
Messages
2,307
Reaction score
855
It's not the first time digital ocean is giving me troubles, I always follow the tutorials to the t but get problems, with most droplet images configurations.
Trying aapanel now, here is what I did so far:

Domain registrar is Yahoo.
On Digital Ocean, created CentOS droplet. Logged in with putty and SSH key, installed aapanel.
Aapanel dashboard on browser working fine. Added domain with automatically created databases, upload and decompress wordpress inside domain folder.
Changed DNS in Yahoo dashboard to Digital Ocean's.

On domain URL I have "Congratulations, the site was created successfully!" message, but with domain/wp-admin I get 404 not found-nginx, and inputting the ipv4 I get 403 forbidden.

What am I missing?

Kindly help, cordially
 
the easiest way to use digital ocean is with the Marketplace
go to the market place and create "CyberPanel" droplet with Ubuntu 2020
 
@MisterXYZ No, when I try to access domain/wp-admin to do it I get 404 not found-nginx. Wordpress is decompressed inside domain folder.

@mnrfas I thought cyberpanel wasn't free, I'll try this.
 
the easiest way to use digital ocean is with the Marketplace
go to the market place and create "CyberPanel" droplet with Ubuntu 2020
This is easier in my opinion. If you still cannot get it done, PM me. :) You can also use the Openlitespeed WordPress installation image for Ubuntu.
 
@MisterXYZ No, when I try to access domain/wp-admin to do it I get 404 not found-nginx. Wordpress is decompressed inside domain folder.

@mnrfas I thought cyberpanel wasn't free, I'll try this.
Last time i used it was in late 2019 and it was 100% free
 
@MisterXYZ No, when I try to access domain/wp-admin to do it I get 404 not found-nginx. Wordpress is decompressed inside domain folder.

For installing wordpress you have to access domain not domain/wp-admin.

I hope you do not have wordpress folder under domain folder.
 
Hey I'm following a tutorial for cyberpanel, I'm at the step where I need to change nameservers on my registrar to "mydomain".com, but Yahoo small business (free com domain) won't let me with this error message.

I tried putting the domain in primary name server and domain is unlocked. What gives?
5da8209e3dc86-funny-boss-memes-fb29 (1).png
 
I've never had any problem with DO and it's currently my preferred hosting. If you're going to run a WP site, i suggest to look into the marketplace and install Ubuntu with LAMP. They also have a Wordpress droplet but ive not tried it.
 
@thedestroyer Ok, can you tell me how to have multiple sites with that configuration?
And will it be needed to change nameservers on Yahoo registrar, because as I just said Yahoo for some reason isn't letting me change nameservers to my domain's.
 
@thedestroyer Ok, can you tell me how to have multiple sites with that configuration?
And will it be needed to change nameservers on Yahoo registrar, because as I just said Yahoo for some reason isn't letting me change nameservers to my domain's.

I've not had any domains registered under yahoo. Bulk of my domains are in namecheap. Changing nameservers and dns shouldn't be such a hassle so i suggest you transfer the domain to a much reliable registrar. After that, point the domain NS to DO, and clear cookies\cache everytime you do a site configuration so it will appear fast.

For multiple sites, you can look into 'Wordpres Multisites' configuration via google search. Bunch of guides are out there for it. Basically, you need to create virtual hosts under DO droplet to be able to make the wordpress multisites work.
 
You are missing proper Nginx vhost configuration.
 
I've never had any problem with DO and it's currently my preferred hosting. If you're going to run a WP site, i suggest to look into the marketplace and install Ubuntu with LAMP. They also have a Wordpress droplet but ive not tried it.
Ubuntu with LAMP is not the only option. OP has installed Cyberpanel which is a control panel for Litespeed.
You are missing proper Nginx vhost configuration.
OP is using Cyberpanel, idk from where you got the idea about nginx vhost configuration. He's saying that the problem is related to updating the NS.

@Zakch93 Remove the optional nameservers (ns3 and ns4) and then try to update.
 
@V Yeah I did, it's not letting me look.
Curiously, when I try a nameserver like "ns1.bluehost.com" or a random one just "ns1.domain.com", it goes through, but when I put in my domain, I get error.
7.jpg


In the Youtube tutorial I'm following, he changes the nameservers on the registrar to "ns1.mydomain.com" as well on top of having added glue/a records "mydomain+myip", which already did.

Maybe I need to contact them to have them change to dedicated nameservers?

Maybe Yahoo don't allow the nameservers to be similar to A records?

I left the nameservers to nsx.digitalocean.com for now.
 
Last edited:
OP is using Cyberpanel, idk from where you got the idea about nginx vhost configuration. He's saying that the problem is related to updating the NS.
He has mentioned that he is getting 404 and 403 when accessing the site, both with domain and without the domain. He is basically getting an issue with a web server (Nginx, Apache, etc.) configuration or permissions. Under every control panel (cPanel, Plesk, aaPanel, etc.), there is some kind of web server. Control panels are only/mainly managing service's configuration files. If he can access the website by statically adding an IP address in the "/ etc/hosts" (CloudFlare is blocking me writing a proper path) file, then DNS/NS can be eliminated as a potential problem because it's not related to DNS.
The OP can test this by utilizing static DNS configuration in "/ etc/hosts" and adding a test txt file inside the document root.

@Zakch93 When it comes to name servers, you can continue using Yahoo's NS, and only point the A record to your server's IP address. Of course, if you want your own name servers, you will need to register them first.
 
@iRakic Is it ok if I put digitalocean nameservers in registrar?
 
@Zakch93 Yes, it's okay. Please make sure that after you have made changes to check if the domain is pointing to the proper A record. DNS propagation can take some time depending of ISP's cache update. Using Google's DNS (8.8.8.8) or CloudFlare's DNS (1.1.1.1) on your local PC can speedup the DNS propagation for you especially if your ISP is caching it.
 
@V Yeah I did, it's not letting me look.
Curiously, when I try a nameserver like "ns1.bluehost.com" or a random one just "ns1.domain.com", it goes through, but when I put in my domain, I get error.View attachment 147366

In the Youtube tutorial I'm following, he changes the nameservers on the registrar to "ns1.mydomain.com" as well on top of having added glue/a records "mydomain+myip", which already did.

Maybe I need to contact them to have them change to dedicated nameservers?

Maybe Yahoo don't allow the nameservers to be similar to A records?

I left the nameservers to nsx.digitalocean.com for now.
The nameservers should be ns1.digitalocean.com and ns2.digitalocean.com. Please try this and let me know if you're still experiencing any problem. :)


He has mentioned that he is getting 404 and 403 when accessing the site, both with domain and without the domain. He is basically getting an issue with a web server (Nginx, Apache, etc.) configuration or permissions. Under every control panel (cPanel, Plesk, aaPanel, etc.), there is some kind of web server. Control panels are only/mainly managing service's configuration files. If he can access the website by statically adding an IP address in the "/ etc/hosts" (CloudFlare is blocking me writing a proper path) file, then DNS/NS can be eliminated as a potential problem because it's not related to DNS.
The OP can test this by utilizing static DNS configuration in "/ etc/hosts" and adding a test txt file inside the document root.
Ah, my bad I totally forgot about his initial problem. :D
 
@iRakic Ok thanks

Guys, I managed to make it work, thanks a lot to all you. :)

It seems the issue I was having also with my previous attempts was that I wasn't creating A records on the Registrar. That wasn't indicated in any tutorial I saw until this last one, and until iRakic pointed it out.

Just one more thing, SSL is not working neither on the panel or on the site. Do I need to create a record for the root domain with the @ symbol + ip on registrar as well, besides ns1 ns2 and www? Does it have something to do with this?
 
Back
Top