| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Urs Brauchli <urs(dot)brauchli(at)update(dot)ch>, pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: PG-Admin 4 - SSH-Tunneling |
| Date: | 2016-09-30 15:35:55 |
| Message-ID: | CA+OCxowjqcx2N4hkF+aZ7Y1MwBt_vPCb3qkKHOBo1UgC1OgTGg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
> Could this be a problem with the SSL CERT? (Or the version of SSL?)
> This link, while for curl instead of posstgres, may have a clue about what
> might be going on
>
> http://blog.techstacks.com/2010/03/3-common-causes-of-unknown-ssl-protocol-errors-with-curl.html
I suspect it's that the port numbers are getting mixed up, and Urs is
actually pointing pgAdmin at a port that (either directly, or through
the tunnel) has OpenSSH listening on it - the reason being that
OpenSSH responds to a connection with:
SSH-2.0-OpenSSH_5.3
Or similar, depending on the version.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | spur230 | 2016-09-30 15:43:10 | Import Server Group with password from pgadmin III to pgAdmin 4 /windows 7 |
| Previous Message | Dave Page | 2016-09-30 11:05:41 | Re: PG-Admin 4 - SSH-Tunneling |