Change the Client SSH port

[Riaan Pretorius]

Good Day, wondering if anyone knows if it possible to sent the client port for SSH to something else?

I was using:

minarca configure -r backup.rplab.xyz -u mark -p 'xxxxx' -n MarkBackup

Then i asked chatgpt and it said this:

minarca-remote-host add backup.rplab.xyz --port 2224 -u mark -p 'xxxxxx'

But minarca-remote-host  does not seem to exist. is there a way? would be very helpful if we can change the SSH port on the client.

[Patrik Dufresne]

Hello Riaan,

If you want to configure the client to use a different SSH port, you'll need to update your server settings accordingly. You can find more details in the documentation:

• Advanced Minarca Configuration
• Secure Remote SSH Access

Once the server is properly configured, updating the minarca-remote-host will allow the client to connect using the specified port.

Regarding the command from ChatGPT:

minarca-remote-host add backup.rplab.xyz --port 2224 -u mark -p 'xxxxxx'

This appears to be incorrect (likely an AI hallucination). It's best to refer to the official command-line documentation:

• Minarca Client CLI
• Or simply use minarca --help for guidance.

Let me know if you need further clarification.

--
You received this message because you are subscribed to the Google Groups "Minarca Data Backup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to minarca+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/minarca/62d22c02-4af1-49e3-bf86-6c953a52b2ebn%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

IKUS Software

https://www.ikus-soft.com/

514-971-6442

St-Colomban, QC J5K 1T9

[Riaan Pretorius]

Thank you for the advice.

I am using the docker container for testing. I assume I have to add those custom values to /etc/minarca/minarca-server.conf correct?

[Patrik Dufresne]

Hello Riaan,

> I am using the docker container for testing

I’m not sure where you got this Docker container from, but it’s not supported—at least not by me.

A couple of months ago, I started working on a Docker image, so you may have picked up a development version from DockerHub. However, it’s not an official release. According to my roadmap, I plan to distribute a stable Docker image of Minarca around mid-2025.

To view this discussion visit https://groups.google.com/d/msgid/minarca/84a86ba7-9f44-4f1a-895a-ef51c2fbb0cfn%40googlegroups.com.

[Riaan Pretorius]

Docker HUB is where i found it - did not want to build a VM just so i can test this - using this one:

ikus060/minarca-server:6.0.0b9.dev14-g327cbdc-debian12

I will assume the answer is no. No worries. I can build my own container then.

Can even share it with you when done won't take long to setup (Dockerfile and Docker-compose.yaml files.

And if you would like to use it - i can either make it build from source or use the official deb packages. I always try and use the official packages - easier to deal with.

[Patrik Dufresne]

Hello Riaan,

> Docker HUB is where i found it - did not want to build a VM just so i can test this - using this one:
> ikus060/minarca-server:6.0.0b9.dev14-g327cbdc-debian12

This is a "dev" version as noted in the tag.

> I will assume the answer is no. No worries. I can build my own container then.

> Can even share it with you when done won't take long to setup (Dockerfile and Docker-compose.yaml files.

> And if you would like to use it - i can either make it build from source or use the official deb packages. I always try and use the official packages - easier to deal with.

Thanks for your offer. 

You may take a look at my development branch in GitLab: https://gitlab.com/ikus-soft/minarca-server/-/tree/patrik-docker

Also take a look at the issue: https://gitlab.com/ikus-soft/minarca/-/issues/7

Someone else is also looking into Dockerizing Minarca Server.

To view this discussion visit https://groups.google.com/d/msgid/minarca/c1d8c77f-d57f-43d9-940b-e011b1429e74n%40googlegroups.com.

[Riaan Pretorius]

Hi Patrik,

I got the container running.  I used the deb/apt method to build the container.

I took what was already done and made it a little better.

I also understand now why there was no config file now, I will add auto detect support soon if it finds a configuration file it will automatically add -f <config file.conf> when found. This would help with people that want to manage the container via a configuration or just environment variables or a combination of the 2.  This would also allow for a future setup using Kubernetes and configmaps.

So now I am trying to figure out why i have permission issues and how to fix them. I could possibly incorporate my fixes into the container so it fixes what needs fixing with startup.

This was the magic variable i needed:

MINARCA_MINARCA_REMOTE_HOST

My current issue is this:

Could not open user 'minarca' authorized keys '/backups//.ssh/authorized_keys': Permission denied
Could not open user 'minarca' authorized keys '/backups//.ssh/authorized_keys2': Permission denied
 

Once i get passed that and a successful client connection and a backup test I will look

Also I did see there is a changes in your docker repo: https://gitlab.com/ikus-soft/minarca-server/-/tree/patrik-docker/docker and some of the issues looks related to my issue based on this:

https://gitlab.com/ikus-soft/minarca/-/issues/7

[Riaan Pretorius]

I might also have found a bug:

When the authorized_keys is populated multiple entries are created. This appears to happen when ever you connect. so it just keeps populating the authorized_keys forever.