Jump to content

First time in VPS


ballagyr
 Share

Recommended Posts

Greetings
I recently activated my VPS, basically I've done almost everything to get a server running. However, I would like to know, how do I point some domain I have to Apache. Already considering that I intend to add others independently. I have an active Tommy account, but I don't plan on migrating as I'm setting up a server from scratch. The email tells me that I have a domain (******.heliohost.us), however, it doesn't access Apache, it doesn't even receive a simple "ping".

In the email that I received it says that I must use the ip provided in a domain type (A), but does this apply to more than one domain? Subdomains?

Link to comment
Share on other sites

Hi @ballagyrm, We will add an A record to vps67.heliohost.us soon, it was a miss from my end - that's why it is not responding to ping. We usually add the A record before sending the VPS email itself.

Regarding hosting, the VPS comes with only a fresh OS installed. To use, Apacha/Nginx you will have to install them manually and configure them or you can use a free control panel software like HestiaCP on your VPS.

Link to comment
Share on other sites

Yes, I've already configured Apache/MariaDB, including the preconfiguration of the certbot for to use the Let's Encrypt. I'm just having questions regarding setting up domains and subdomains in the VPS.

If I put this "HestiaCP", will this task be easier and optimized?

Link to comment
Share on other sites

There are two parts to this setup:

1. On your registrar's site (such as Namecheap.com, GoDaddy.com, etc., the one you bought your domain from) set up the appropriate records (normally A and AAAA are enough, just A if you do not care about ipv6) to point to your host. You should have received the appropriate addresses in your VPS invitation. These records have to be set up or each subdomain.

2. On your server (Apache or nginx) set up virtual hosts (again, one for each subdomain). Let's Encrypt certificates have to be generated for each virtual host if you want the pages to be served over https. See some examples here. These virtual hosts will be served from the same IP, and Apache will use the request headers to decide which host to direct the request to.

 

Alex

  • Like 1
Link to comment
Share on other sites

The DNS entry has been setup => vps67.heliohost.us now points to your VPS IP.

59 minutes ago, ballagyr said:

If I put this "HestiaCP", will this task be easier and optimized?

Yup it can automate Lets Encrypt certificates as well. But as you already have setup Apache and Let's Encrypt, it should be good to go!

Regarding pointing another domain to your VPS, just create an A record on the domain (say abcd.com) by going to their domain control panel (like GoDaddy) to 65.19.191.150. Then you'll need to add a VirtualHost in Apache corresponding to that domain.

Link to comment
Share on other sites

I read that HestiaCP is not recommended for use on CentOS. I've seen some alternatives, but practically all recommends installing on a clean system, without any kind of configuration and as you already know, I've done almost everything. Because of this, for now I'm going to avoid using some control panel.

Thanks for help guys, I believe that now I can do what I intend, I really had forgotten about Apache's Virtual Host trick.

Link to comment
Share on other sites

9 hours ago, c2itnow said:

2. On your server (Apache or nginx) set up virtual hosts (again, one for each subdomain). Let's Encrypt certificates have to be generated for each virtual host if you want the pages to be served over https. See some examples here. These virtual hosts will be served from the same IP, and Apache will use the request headers to decide which host to direct the request to.

This examples here is port 80. It is the standard port for http.
The standard port for https using SSL is 443.
Keep this in mind if you have referenced and configured this example. It will be necessary to add the setting of Apache.
You also need to specify the location of Let’s Encrypt issued with this setting.

My VPS (Rocky instead of CentOS) uses Caddy instead of Apache to simplify these configurations.
Caddy is a web server and supports Let’s Encrypt (or ZeroSSL) issuance and automatic updates.

Since you have selected CentOS, The EOL for CentOS 8 is December 31, 2021:
https://blog.centos.org/2020/12/future-is-centos-stream/

Link to comment
Share on other sites

Problem solved, after thinking a lot about what it could be, I forgot something very basic. I just needed to enable https service on CentOS firewall.

I use CentOS 7, I chose this distro because i have more familiarity with it. This version will last a lot longer and it's nothing I should be worried about.

Anyway, thank you for your attention!

Link to comment
Share on other sites

  • 2 weeks later...

Hi guys, I have a strange problem in phpMyAdmin, maybe in MariaDB. Look at this high "Failed Attempts". What could be happening?

Screenshot: http://ballagyr.sdf.org/shared/pma_failed_attempts.png

MariaDB, 10.5.12 and phpMyAdmin, 5.1.1.

Thanks!

PS: I posted it here because this issue is related to my VPS and I found it convenient to use this same space.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...