Bobcares

Certbot Apache Different Port | Guide

by | Nov 30, 2023

Learn how to use Certbot with Apache on a different port. Our Server Management Support team is here to help you with your questions and concerns.

Certbot Apache Different Port | Guide

Did you know that when we work with Certbot and the Apache web server, the default configuration assumes that our Apache server is listening on the standard HTTP and HTTPS ports?

Certbot Apache Different Port | Guide

These ports are 80 and 443. However, we may need to use a different port for our Apache server and still use Certbot to obtain and manage SSL certificates.

How to use Certbot with Apache on a different port

In such situations, we can follow these steps to use Certbot with Apache on a different port:

  • First, we have to install Certbot. We can install it on Debian-based systems with this command:

    sudo apt install certbot python3-certbot-apache

  • Then, change the Apache configuration to make it listen on the specific port. In order to do this, we have to edit the Apache configuration files. Once we find the ports.conf file or a virtual host configuration file defining the custom port we can edit it easily.

    For example, if we want to use port 8080, we can edit the configuration like this:


    <VirtualHost *:8080>
    # Your Apache configuration for port 8080
    </VirtualHost>

  • Now, we have to make sure the new port we are using is open to external requests trying to reach the Apache server in case the server has a firewall enabled. We can use a tool like ufw to easily manage firewall rules on Ubuntu:

    sudo ufw allow 8080/tcp

  • Then, it is time to restart your Apache server.

After the above steps, we have to make sure that the website is accessible on the custom port.

Now, we can easily use Certbot to get an SSL certificate for our domain on the custom port with this command:

sudo certbot --apache -d ourdomain.com --http-01-port 8080

Here, the –http-01-port flag indicates the port on which Certbot will perform HTTP challenges to validate domain ownership.

Now, Certbot will take us through the certificate issuance process and also configure our Apache server to use the SSL certificate for the custom port.

Finally, we can check the website’s HTTPS functionality by accessing it via https://ourdomain.com:8080.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts demonstrated how to use Certbot with Apache on a different port.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF