Re: [CentOS-es] OT certificado zimbra

2017-10-14 Thread Carlos Martinez
Saludos. Dependiendo del procedimiento para crear el certificado, Requieres tener en el equipo cliente, uno de los siguientes dos archivos: 1) La llave pública del nombre del host, si solo se creó el certificado para zimbra o es el autogenerado por zimbra. Este se puede bajar fácilmente con

Re: [CentOS-es] Centos 6.9 una de VirtualHost

2017-10-14 Thread Miguel González
Hola: Supongo que tienes un NAT a nivel de router hacia el servidor web no? Olvidate por tanto de la IP pública, lo que importa es la IP local. Aquí tienes más información, pero lo que tu quieres es un name-based virtualhost: https://httpd.apache.org/docs/2.4/vhosts/name-based.html

Re: [CentOS] systemctl reboot -- server not accessible after reboot

2017-10-14 Thread Jonathan Billings
On Oct 14, 2017, at 1:54 PM, Mike <1100...@gmail.com> wrote: > Server disconnects my ssh connection and never comes back up. > Go to the server and the power is on but the server is not accessible by ssh. > When I connect a monitor and keyboard --- non-responsive. It's like > it's in suspend

Re: [CentOS-es] Centos 6.9 una de VirtualHost

2017-10-14 Thread Carlos Martinez
Saludos. Asumo que deseas manejar virtualhost basados en nombres (https://httpd.apache.org/docs/2.4/vhosts/name-based.html) . La definición debe ser de la siguiente forma: ServerName www.oficina.salman.psl ServerAlias oficina.salman.psl DocumentRoot "/home/ftp_salman_psl/www"

Re: [CentOS] systemctl reboot -- server not accessible after reboot

2017-10-14 Thread John R Pierce
On 10/14/2017 10:54 AM, Mike wrote: When I try systemctl reboot directly on the server. Same problem --- does not start to login prompt. so where does it stop?   does it never finish BIOS short self-test after the shutdown?   does it hang somewhere in the Linux loading sequence?   if it goes

Re: [CentOS] systemctl reboot -- server not accessible after reboot

2017-10-14 Thread Alexander Dalloz
Am 14.10.2017 um 19:54 schrieb Mike: Hi, Such a simple problem, but I can't figure out the cause. Supermicro server with a Xeon E3-1200 cpu. 1U entry level item. Using CentOS 7 The version is a bit unprecise. Are you fully updated? On 7.3 and 7.4 I haven't seen that issue. from ~$root ---

Re: [CentOS] systemctl reboot -- server not accessible after reboot

2017-10-14 Thread Vitalino Victor
Hi, I have this problem! Try: # shutdown -r now For a test, please... 2017-10-14 14:54 GMT-03:00 Mike <1100...@gmail.com>: > Hi, > > Such a simple problem, but I can't figure out the cause. > Supermicro server with a Xeon E3-1200 cpu. > 1U entry level item. > > Using CentOS 7 > > from

[CentOS] systemctl reboot -- server not accessible after reboot

2017-10-14 Thread Mike
Hi, Such a simple problem, but I can't figure out the cause. Supermicro server with a Xeon E3-1200 cpu. 1U entry level item. Using CentOS 7 from ~$root --- systemctl reboot Server disconnects my ssh connection and never comes back up. Go to the server and the power is on but the server is not

Re: [CentOS-es] Centos 6.9 una de VirtualHost

2017-10-14 Thread L.C. - Salman PSL
*:: O no me he explicado bien, o no lo has leido completo. No se trata de que sean .es .pepito, o .psl En el router redirijo el puerto 80, no los dominios .es La IP publica es la IP del servidor ( para SSH por ejemplo ) Ya probe * NameVirtualHost 213.60.147.68 Y no va pues no es un