mirror of
https://github.com/eduardolat/pgbackweb.git
synced 2026-04-25 13:45:54 +03:00
[GH-ISSUE #38] Remote SSH tunnel support #29
Labels
No labels
bug
confirmed next step
duplicate
enhancement
help wanted
in progress
in progress
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/pgbackweb#29
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Morethanevil on GitHub (Sep 9, 2024).
Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/38
The webinterface is awesome, the S3 support too. I wanted to know if SSH-tunnel support is planned? I have 3 different servers, one homeserver at home, a VPS and a dedicated server. All of them are running Postgres, but I only want to have pgbackweb at home on my LAN. If I want to back up the other 2 servers, I would need to expose pgbackweb to the web, which I don't want. A VPN is not an option in my case. A remote connection would be cool in this case. Pgbackweb could connect via SSH to the other hosts and then perform its actions
@AiAutomationAgency commented on GitHub (Nov 11, 2024):
Supporting SSH for backs instead if S3 would be create.
@codedoga commented on GitHub (Aug 2, 2025):
+1
Connecting to remote database is in my opinion only secure via SSH (or some other secure) tunnel. Supporting connecting via SSH tunnel is actually the only feature I'm missing.
Great work though, and I really appreciate all the effort.
@codedoga commented on GitHub (Aug 7, 2025):
Also mentioned here: https://github.com/eduardolat/pgbackweb/issues/5
@Morethanevil commented on GitHub (Aug 8, 2025):
I am not sure if this project is still alive. Last commit 6 months ago, last activity 3 weeks ago. I stopped using it. Looked promising, but too little activity.
Closing this now
@eduardolat commented on GitHub (Aug 8, 2025):
@Morethanevil Of course, the project is alive; it's simply stable.
The main problem is that I, as the maintainer, am currently going through an extremely busy phase of my life. I'm easily working on my projects 12 hours a day, 7 days a week, and right now it's impossible for me to move forward with this project, which isn't really generating any benefits for me (apart from the Postgres backups, of course).
However, I plan to continue developing it as soon as I have a little more free time and improve the project as much as I can, adding many of the features requested in the issues and other things I have planned, such as MySQL, Mongo, SQLite backups, etc.
I hope you can understand that I don't have the time right now, but I will continue working on this (unless I die), and i'm very sorry to hear that you're no longer using the project. I really did create it with a lot of love and without expecting anything in return. But I understand that I haven't dedicated much time to it lately. I hope that can change soon.
@Morethanevil commented on GitHub (Aug 8, 2025):
Sorry to hear that you are so busy, but look from the other side: a web application, that not gets updates within months is a security risk. The Go library and its dependencies got several updates too.
@eduardolat commented on GitHub (Aug 8, 2025):
You're right, I'll try to at least keep the dependencies up to date while I get time to move forward with the new features.