Unable to connect to client

[Marlo Mitchell]

Hello all, I've completed a successful setup of the Minarca server however I am unable to get a windows client to connect to the Minarca server. I'm not sure what I am missing.

I receive the following errors:

I have a reverse proxy configured with the following settings:

nano /etc/apache2/sites-available/000-default.conf

<VirtualHost *:80>

     ServerName eowyn.theliguaneaclub.com

     ProxyPass / http://localhost:8080/ retry=5

     ProxyPassReverse / http://localhost:8080/

     RequestHeader set X-Real-IP %{REMOTE_ADDR}s

     ErrorLog ${APACHE_LOG_DIR}/error.log

     CustomLog ${APACHE_LOG_DIR}/access.log combined

     #Redirect permanent / https://eowyn.theliguaneaclub.com/

</VirtualHost>

nano /etc/apache2/sites-available/eowyn.conf

<VirtualHost *:80>

     ServerName eowyn.theliguaneaclub.com

     ServerAdmin sysa...@theliguaneaclub.com

     # Redirect HTTP to HTTPS

     RewriteEngine on

     RewriteRule ^(.*)$ https://eowyn.theliguaneaclub.com$1 [L,R=301]

     <Location />

         Order Allow,deny

         Allow from all

     </Location>

 </VirtualHost>

 

 <VirtualHost *:443>

     ServerName eowyn.theliguaneaclub.com

     ServerAdmin sysa...@theliguaneaclub.com

 

     ProxyRequests Off

     ProxyPreserveHost On

     ProxyPass / http://localhost:8080/ retry=5

     ProxyPassReverse / http://localhost:8080/

     RequestHeader set X-Forwarded-Proto https

     RequestHeader set X-Real-IP %{REMOTE_ADDR}s

 

     # SSL Configuration

     SSLEngine on

     SSLCertificateFile    /etc/myssl/server.crt

     SSLCertificateKeyFile /etc/myssl/server.key

    # SSLCertificateChainFile /etc/letsencrypt/live/eowyn.theliguaneaclub.com/fullchain.pem

     <Location />

         Order Allow,deny

         Allow from all

     </Location>

</VirtualHost>

[Patrik Dufresne]

Hello Mario,

You may take a look at the following in-progress documentation for Minarca v6.1, which is planned for release around June 2025:
https://nexus.ikus-soft.com/repository/archive/minarca/6.1.0a2/doc/networking.html

The documentation has been improved for better clarity. Your feedback is welcome—please let me know if anything seems missing or unclear.

Regarding the error message showing the URL https://eowyn.theliguaneaclub.com:8080, it seems off. Port 8080 is unusual for HTTPS, as the default port is 443.

Also, are you using self-signed certificates or a private PKI? It's not clear from your apache configuration. Make sure the URL is accessible from your web browser.

--
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/CAFjBRNN%3DKnXVj9tPLfKq36Jedy%3DaCRD61M-waoqs%2BV_ojFR3NA%40mail.gmail.com.

--

ATTENTION : Je serai en vacances du 2 au 21 mai 2025.
ATTENTION: I will be on vacation from May 2 to May 21, 2025.

IKUS Software

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

514-971-6442

St-Colomban, QC J5K 1T9

[Marlo Mitchell]

Thanks for your feedback Patrick,

1. I am using self-signed certificates with utilizing the following command:

openssl req -new -x509 -nodes -days 365 -out server.crt -keyout server.key

I plan to access the minarca interface locally, nothing to be exposed via the public internet.

2. I tired using 443 but the application immediately returned an error, but when i specified 8080 it seemed to actually try to connect to the source server.

I'll review the documentation you shared, thank you.

Unfortunately i don't have more time to try and get Minarca to work, i've decided to use Borg backup for now, I may revisit this solution in the future.

I think integrating a HTTPS login page would really help making this project easier to use, having to deploy an additional thing to make it secure is a big shortcoming in my opinion.

But I don't know how difficult that is to develop so that's just my two cents. I hope the project continues to grow, it has tremendous potential. :-)

Thanks again for your feeedback, have a wonderful day.

[Patrik Dufresne]

The problem is related to your self-signed certificate. Current version need a workarround to supported private PKI or self-signed certificate. Base on user feedback, will work to improve how it's working in future version.

To view this discussion visit https://groups.google.com/d/msgid/minarca/0c7e56ae-edaa-4f3b-865e-e408c3041057n%40googlegroups.com.