Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Vestacp https port
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Vestacp https port

Hello, i am using latest VestaCP on a Centos 6.5 (64-Bit), i have successfully installed Comodo PositiveSSL keys. Now i can access my website this way: https://domain.com:8443. It's not convenient. It is possible to make it accessible via standard port 80? Like: https://domain.com

Comments

  • It's probably a good idea to keep the port config the way it is, but if you really want to change it, have a read here: https://forum.vestacp.com/viewtopic.php?f=11&t=5126

  • Why not install apache and redirect any request to port 8443? There's another way, you may use the proxy module with Apache to show the content but I wouldn't recommend this, it would be safer to install apache and redirect the requests to port 8443. To do so, install apache (yum install httpd) and open its configuration file (usually at /etc/httpd/conf/httpd.conf) then add the following line at the end of the file:

    Redirect / https://domain.com:8443
    

    Save and exit, then restart apache:

    service httpd restart
    
  • Thanks for the answers. But it's a bit strange to keep the url with a port number, i didn't saw any web-sites (e-shop) which used a port number with https.

  • @heihachi88 said:
    Thanks for the answers. But it's a bit strange to keep the url with a port number, i didn't saw any web-sites (e-shop) which used a port number with https.

    A few web hosts that I know follow this style.

  • said: It is possible to make it accessible via standard port 80? Like: https://domain.com

    For HTTPS it would be 443.

  • mikhomikho Member, Host Rep

    Vestacp uses a single config file.
    You could edit that to use port 80 (ssl should be on https, 443 as mentioned) but I'm sure it would break everything else in your installation.

  • alessioalessio Member
    edited October 2014

    MikHo said: but I'm sure it would break everything else in your installation.

    That would qualify for a bug report then however.

  • So it is possible to forward 8443 to 443?

  • add nginx support with force-https template

  • already tried that, no difference. Have you tried it yourself?

  • If you have another IP you can change the nginx config for vesta and change the port to 443 and set the SSL cert.

  • I'd simply change the port.

  • mikhomikho Member, Host Rep

    If you read the documentation there are different configs for the vestcp installation and the websites.

    I wouldn't recommend to change the vestacp port to 443 as this would most likely break things when you add a second or third domain, even a sub-domain.

  • MikHo said: If you read the documentation there are different configs for the vestcp installation and the websites.

    As I said, bug report :)

  • 2 months ago i had this working out of the box, but guess, recent updates killed this. So there's no way to set 443 port for SSL without a pain?

  • mikhomikho Member, Host Rep

    Nginx is probably not running or you are missing the https config file.

  • @heihachi88 said:
    2 months ago i had this working out of the box, but guess, recent updates killed this. So there's no way to set 443 port for SSL without a pain?

    Something is very wrong with your configuration or installation. I ran a fresh CentOS install of Vesta a few days ago and SSL works fine by simply checking the box.

  • @heihachi88 said:
    Hello, i am using latest VestaCP on a Centos 6.5 (64-Bit), i have successfully installed Comodo PositiveSSL keys. Now i can access my website this way: https://domain.com:8443. It's not convenient. It is possible to make it accessible via standard port 80? Like: https://domain.com

    8443 is only used to the VestaCP admin panel, websites run on 80/443 as normal.

    You may want to try changing your Apache/nginx template as it appears there's a configuration issue if you're not able to access your website(not VestaCP) over the standard ports.

  • @nunim, you're wrong. VestaCP admin panel uses 8083 port, not 8443. Contacted with developers, they told me that Vesta's https working only with a port number 8443. It's a bug.

  • jarjar Patron Provider, Top Host, Veteran

    Reverse proxy, 443 serves 8443. Fix vhost in /home/username/conf/web.

    Thanked by 1mikho
Sign In or Register to comment.