Greetings, thanks for the reply. we have a proxy, but the proxy never bothered. only when we need to connect to the outside.
chequie the fail2ban and apparently was not blocking anything .. my local PC is: 190.170.71.69 the server is: 190.170.71.109 PCs and server are on the same network. I have the server side even mine. before attempting to use a user that is not root, always needed to make a reverse tunnel to use administrative interface .. wonder: is this normal? I've always used fail2ban The only novelty here is: * Block root access via ssh. * Create a "user XZY" with permission to connect via ssh * User XYZ uses "sudo" for administrative tasks my language is Spanish (sorry) 2012/11/19 Alexandre Kouznetsov <[email protected]> > Hello. > > El 19/11/12 09:17, Luis Díaz escribió: > >> netstat -tanpu >> http://i.minus.com/**ibawGESjmRs3xd.png<http://i.minus.com/ibawGESjmRs3xd.png> >> > Great, you proxmox seems top be up ans listening on port 8006 > > > root@mipc:~$ telnet 190.170.71.109 8006 >> Trying 190.170.71.109... >> Connected to 190.170.71.109. >> Escape character is '^]'. >> > Even better, the port 8006 seems to be reachable from your workstation. > (assuming 190.170.71.109 is your proxmox server) > > tunnel reverse: >> root@mipc:/home/user1# ssh -l 1234:127.0.0.1:8006 >> <http://127.0.0.1:8006> [email protected] >> <mailto:[email protected]**> >> Received disconnect from 190.170.71.109 <http://190.170.71.109>: 2: Too >> >> many authentication failures for userxyz >> > It seems like your fail2ban is still working. Check it's documentation for > reference how to disable it, or at least clear your client host ban. > > Finally, try https://xxx.xxx.xxx.xxx:8006 >> <https://xxx.xxx.xxx.xxx:8006/**> in your browser, and tell specifically >> >> what error (if any) do you get. An exact quotation is important. >> >> http://i.minus.com/**iCtpfuylTldqv.png<http://i.minus.com/iCtpfuylTldqv.png> >> http://i.minus.com/**ib1LN6Rz5vCDiL.png<http://i.minus.com/ib1LN6Rz5vCDiL.png> >> > Are you using a proxy server? Try disabling proxy, at leas for HTTPS. > Have you tried any other browser? Chrome's error messages seems to be not > too descriptive. > > Are your hosts 190.170.71.109 and 190.170.71.69 on the same network? What > about host "mipc"? Is it behind a NAT, or it uses 190.170.71.69 directly? I > have seen the error you describe when more than one NAT in a row was used, > which is a pretty wired setup. > > > -- > Alexandre Kouznetsov > > ______________________________**_________________ > pve-user mailing list > [email protected] > http://pve.proxmox.com/cgi-**bin/mailman/listinfo/pve-user<http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user> > -- Díaz Luis Analista Programador Facultad de Odontología UC User Linux 532223
_______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
