[Bug]: Unable to login

[santosh2494]

Issue Description

Have configured opensign using docker-compose and able to access the home page on https://localhost:3000 but not on HTTPs://localhost:3001 with which we're unable to see register option to create the users. Please suggest If anything needs to be changes in configuration file.s.

Expected Behavior

Need to see register page

Current Behavior

No option register for new users

Steps to reproduce

http://localhost:3001

Screenshots of the issue(optional)

Operating System [e.g. MacOS Sonoma 14.1, Windows 11]

Ubuntu 20.04

What browsers are you seeing the problem on?

Chrome

What version of OpenSign™ are you seeing this issue on? [e.g. 1.0.6]

2.1.0

What environment are you seeing the problem on?

Hosted (app.yourdomain.com)

Please check the boxes that apply to this issue report.

• [X] I have searched the existing issues & discussions to make sure that this is not a duplicate.

Code of Conduct

• [X] I agree to follow this project's Code of Conduct
• [X] I have searched the existing issues & discussions to make sure that this is not a duplicate.

[wardverduyn]

Is this a known issue? @andrew-opensignlabs

[andrew-opensignlabs]

It should be accessible on port 3001; otherwise, it indicates that your installation wasn't completed correctly. Port 3000 is reserved for internal use and will be blocked in future versions.

[vantzs]

I am using nginx proxy manager to access opensign without caddy. I followed the installation instructions and am accessing port 3001 from my nginx proxy config.

I too am missing the option to register.

Additionally https://opensign.mspnerd.com/ should take you to the default page without registration options. Unfortunately I already have over 80 containers using nginx proxy and can't use caddy as nginx is already bound to 80 and 443. Any ideas?

[reddexx]

@andrew-opensignlabs Many who use the container version here have the problem, we get no possible solution to this problem!

After 1 month a solution should be worth mentioning!

I would like to test Opensign, but this will not be possible

[PereProteus]

So glad I found this. Caddy is ok but i have it in front of cloudflare instead, so ive removed caddy from a docker build. I've been tearing my hair out for a couple of hours trying to get a registration page, no matter how i set it up, it doesnt work. How do you get that page without caddy. I'd love to test the product as well.

[swyliealeon]

Having the same issue here, is there a fix for this or are we just giving up on opensign working?

[reddexx]

@swyliealeon well i haven't had time for a while but it doesn't seem to interest the developer (@andrew-opensignlabs) either, so i'm looking for another software as a solution

I would have liked to test it, but there's no point if none of the devs are interested

I think they are more focused on what makes money

although I am supposed to find a solution for my company, but without a presentation, nothing works

[swyliealeon]

@reddexx thats exactly what they are focused on, and as a company they should be focused on what makes them money. Ironically, I was going to use this self-hosted to show off before we went with the enterprise plan so I guess it probably ended up costing them money. Anyways, I reached out to them and their answer was essentially you are doing something wrong go read the documentation.

[reddexx]

@swyliealeon To me? Iam not the developer 🤣

[andrew-opensignlabs]

@reddexx @swyliealeon Our self-host community is most active on Discord. Please join our discord server if you want quick help from the community.

Please share your browser logs & docker console logs on discord community.

[juanfranp16]

For anyone wondering how to run it behind nginx instead of the default cabby proxy, you dont have to modify the REACT_APP_APPID , APP_ID and appNAME variables in your .env.prod file. You cand modify the rest of them as you like.

And in your nginx conf file add the following code

location / {
  proxy_pass http://IP_SERVER:3000;
  -- 
  # Your own conf
  --
}

location /app {
  proxy_pass http://IP_SERVER:8080;

 -- 
  # Your own conf
  --
}

[decoderzhub]

Hi @santosh2494 @vantzs @reddexx @swyliealeon @PereProteus @juanfranp16

I know this has been an open problem for a while and it took me every bit of two weeks to figure out how to set this up with an alternative reverse-proxy... So I'm posting how to get it to work with nginx using an IP instead of domain name/localhost. We will be using example local ip 10.0.0.62

first you will want to modify your files:

.env.prod

HOST_URL=https://10.0.0.62
PUBLIC_URL=https://10.0.0.62:3001

docker-compose.yml

For your server change the environment variables

- SERVER_URL=${HOST_URL:-https://10.0.0.62:3001}/api/app
- PUBLIC_URL=${HOST_URL:-https://10.0.0.62:3001}

replace caddy with nginx container

  nginx:
    image: nginx:latest
    container_name: nginx-container
    ports:
      - "3002:443"  # exposing new secure port
    volumes:
      - ./nginx.conf:/etc/nginx/conf.d/default.conf
      - ./certs:/etc/nginx/certs
    depends_on:
      - client
      - server
    networks:
      - app-network

Create openssl config file openssl-ip.cnf

[req]
default_bits       = 2048
prompt             = no
default_md         = sha256
distinguished_name = dn
x509_extensions    = v3_req

[dn]
CN = localhost

[v3_req]
subjectAltName = @alt_names

[alt_names]
DNS.1 = localhost
IP.1 = 127.0.0.1
IP.2 = 10.0.0.62

Create your own nginx.crt & nginx.key

Run this command in the opensign folder directory to generate the cert and key

openssl req -x509 -nodes -days 825 \
  -newkey rsa:2048 \
  -keyout nginx.key \
  -out nginx.crt \
  -config openssl-ip.cnf

create a folder in opensign folder directory named "certs" and place both cert and key in this folder

update nginx.conf

server {
    listen 443 ssl;
    server_name 10.0.0.62:3002;

    ssl_certificate /etc/nginx/certs/nginx.crt;
    ssl_certificate_key /etc/nginx/certs/nginx.key;

    location / {
        proxy_pass http://client:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
    }

    location /api/ {
    rewrite ^/api/(.*)$ /$1 break;
    proxy_pass http://server:8080;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    }

}

This routes to the server similar to caddy

Now run

docker compose up -d 

You may now access the addadmin route to login and by accessing the OpenSignServer.

https://10.0.0.62:3002

I use Synology for my reverse-proxy so I just point it to the it

Then you can access it at the assigned hostname