Databases
StackOverflow2013
Postsdbo
POcap deploy works from office but not from home network
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POcap deploy works from office but not from home network
    primarykey
    data
    text
    <p>I'm trying to get a little work done over the weekend and want to stage some stuff. I can deploy in the office fine but when I run cap deploy from home I get the following error:</p> <p>Permission denied (publickey)</p> <p>If my public key works in the office shouldn't work from as well? I have also checked any firewall policies with our hosting.</p> <pre><code>OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011 debug1: Reading configuration data /etc/ssh_config debug1: /etc/ssh_config line 20: Applying options for * debug1: Connecting to **.***.***.** [**.***.***.**] port 22. debug1: Connection established. debug1: identity file /Users/*******/.ssh/id_rsa type 1 debug1: identity file /Users/*******/.ssh/id_rsa-cert type -1 debug1: identity file /Users/*******/.ssh/id_dsa type -1 debug1: identity file /Users/*******/.ssh/id_dsa-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.0p1 Debian-3ubuntu1 debug1: match: OpenSSH_6.0p1 Debian-3ubuntu1 pat OpenSSH* debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-&gt;client aes128-ctr hmac-md5 none debug1: kex: client-&gt;server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024&lt;1024&lt;8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA *********************************** debug1: Host '**.***.***.**' is known and matches the RSA host key. debug1: Found key in /Users/*******/.ssh/known_hosts:5 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/*******/.ssh/id_rsa debug1: Authentications that can continue: publickey,password debug1: Trying private key: /Users/*******/.ssh/id_dsa debug1: Next authentication method: password </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USisea
    1. USisea
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COI've had this when I have SSH keys that need to be added, after a reboot or something similar. Have you tried `ssh-add ~/.ssh/`?
      singulars
      1. POcap deploy works from office but not from home network
      1. USCDub
    2. COno that didn't seem to help
      singulars
      1. POcap deploy works from office but not from home network
      1. USisea
    3. COIt almost sounds like there's a proxy from your office that SSH goes through from the office that doesn't exist outside... Can you straight SSH to the box, perhaps using `-v` for verbose output?
      singulars
      1. POcap deploy works from office but not from home network
      1. USCDub
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload