I could open up a second port for ssh, but then I'd have the port number in the which I specifically don't want. I will always go to the main domain and handled by the ssh agent there. That means that you can't make a ssh request via the standard port to a subdomain. SSH does not have the header information required for subdomain forwarding. After a long period of trying different settings I realized something very important. Is there any other information or logs I could provide which might help? Outgoing ssh:port -> my_vps_ip:22 -> docker-compose_nginx_service:22 -> bitbucket-server:22ĭoes bitbucket then forward the ssh port 22 to the standard port (7999 i think?) I'm not too familiar with how exactly the git ssh protocol works but is it something like In the docker-compose file I realised last night that I didn't expose the nginx service on port 22. SSH PROXY 24 TOP PASSWORDI haven't explicitly set a password (apart from my user password) but that one isn't being accepted either. It reports that it is connecting it asks me for a password. When I add a README.md, add all changes and Then set created a local repository and set the remote url according to the instructions given in the bitbucket repository ui. I've created a sample project and added myself as the admin to that project. Inside the server configuration UI of bitbucket I've enabled ssh and set the base url to ssh:// I've enabled ssh and uploaded the public ssh key into the bitbucket server via the UI. The problem I am having is trying to clone/push changes to a repository via git using ssh keys. I can access the bitbucket subdomain via web with encryption. The certbot certification is done once to get the certificates up and running and afterwards is accepted. I thought I had the domain names replaced. I've included some more information as suggestedĪh, thanks for pointing it out. I've already tried a myriad of things, including enabeling ssh in the bitbucket serer and setting the url to default to one without a port number behind it. Here is my docker-compose and nginx configuration. If anyone could take a look I'd be incredibly happy to get that very last tid-bit working. I'm pretty sure I've missed something totally obvious but I think I've spent so much time on it I just can't see it anymore. I've been trying to set up the reverse proxy configuration with nginx and docker-compose but it keeps on asking me for a password (and even if I enter it correctly, refuses the connection) and I'm not sure where I'm going wrong at this point anymore.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |