[Bug]: Can't pass the pay wall
Issue Description
I am selfhosting OpenSig and the recent version 2.1.0 we are unable select the free plan after restating the server
Expected Behavior
Run smoothly on selfhosted
Current Behavior
After changing the env.local_dev variables I just started the docker containers. However, after I keep seeing the plan sections and sometimes when I stop the containers it might not connect to server or run migration until i do system prune and start again the volumes. I have been struggling to run consistently for 2 days.
Steps to reproduce
cloned the repository, and checkout to v2.1.0. After changing the env.local_dev variables I just started the docker containers.
Screenshots of the issue(optional)
Operating System [e.g. MacOS Sonoma 14.1, Windows 11]
server linux
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?
production
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.
@onlypfachi You are not supposed to see any plan selection screen on the self-hosted version. Can you please explain the issue in more detail.
@nxglabs I am self-hosting on my server and to install it on the server I cloned the repository, and checkout to v2.1.0. After changing the env.local_dev variables I just started the docker containers. However, after I keep seeing the plan sections and sometimes when I stop the containers it might not connect to server or run migration until i do system prune and start again the volumes. I have been struggling to run consistently for 2 days.
@onlypfachi We have just released v2.1.1 Can you try upgrading to it? Please share console logs/screenshots if it still does not work.
I have moved to v2.1.1 now this is what im getting @andrew-opensignlabs
@onlypfachi If you can see the setup screen it means that front end is able to connect to the OpenSign Server but the specific function has some issue. Can you share the opensign server logs when this error occurs?
@andrew-opensignlabs There are no logs from the server it last ran on migration. Is the url correct?
hey @onlypfachi , can you please send screenshot of log you get in console of chrome
it says bad request
and on network tab
is your domain opensign.elula.cloud @onlypfachi
yes @prafull-opensignlabs
@onlypfachi
can I try to make admin on your domain to check issue
sure @prafull-opensignlabs
hey @onlypfachi , can you please share latest logs from your opensignserver-container and also which reverse proxy did you use?
@prafull-opensignlabs it saved the user but i still cant pass that page
@prafull-opensignlabs for reverse proxy we are using traefik
hey @onlypfachi , can you please pull latest code and try to create new admin once done let us know
Closing this issue due to inactivity. Feel free to reopen if you’re still experiencing this problem.