OpenSign icon indicating copy to clipboard operation
OpenSign copied to clipboard

[Bug]: Local Docker Install Ubuntu 22.04 LTS

Open sesscon opened this issue 9 months ago • 8 comments

Issue Description

Followed all instructions including modifying the .env file. However, when the site renders I can see the favicon but nothing is rendered for the site.

Here is a local curl:

OpenSignâ„¢

Expected Behavior

OpenSign site is rendered and ready for use.

Current Behavior

No webpage is being rendered.

Steps to reproduce

Followed Instructions, confirmed each step.

Screenshots of the issue(optional)

No response

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

Ubuntu 22.04

What browsers are you seeing the problem on?

Chrome, Firefox, Microsoft Edge

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

Latest Release

What environment are you seeing the problem on?

Dev (localhost or vercel)

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.

sesscon avatar Apr 25 '24 18:04 sesscon

Screenshot 2024-04-25 144835

sesscon avatar Apr 25 '24 18:04 sesscon

Estou com mesmo problema

jebob28 avatar May 03 '24 12:05 jebob28

Hey @sesscon

Are you still facing issues with the last release ?

If not i will mark this issue as solved

Zathiel avatar Jun 02 '24 02:06 Zathiel

Same issue here. Logs show a successful connection as in @sesscon 's logs.

Maybe this could help. It's not a ubuntu specific issue. On other devices the JS files are requested from localhost instead of the IP:

grafik

Found a workaround. I don't know if some of these steps aren't neccessary.

  1. make build
  2. Stop the docker containers
  3. sed -i 's#http://localhost:8080#https://your-domain-to-api.com#g' ./path-to-file for /apps/OpenSignServer/index.js, apps/OpenSignServer/runmigrate.js, apps/OpenSign/build/static/js/main.b9b562fb.js, apps/OpenSign/.env and .env
  4. sed -i 's#http://localhost:3000#https://your-domain.com#g' ./path-to-file for apps/OpenSign/build/static/js/main.b9b562fb.js, apps/OpenSign/.env and .env
  5. Delete the docker containers and images
  6. docker compose up -d

Thanks for the workaround.

R/S

Patrick J Huwiler Chief Technology Officer Advanced Business Resources (ABR) +1.414.702.4062 @.*** www.abrsecgroup.com

"The new standard in full-spectrum family office & corporate security."

Confidentiality Notice: The information contained in this email and any attachments may be legally privileged and confidential. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, copying, or use of this email or any attachment for any purpose, or taking any action in reliance on this email or the content contained herein is strictly prohibited. If you have received this email in error, please notify the sender and permanently delete the email and any attachments immediately.

On Thu, Jun 13, 2024 at 10:21 AM cube one @.***> wrote:

Found a workaround. I don't know if some of these steps aren't neccessary.

  1. make build
  2. Stop the docker containers
  3. sed -i 's#http://localhost:8080#https://your-domain-to-api.com#g' ./path-to-file for /apps/OpenSignServer/index.js, apps/OpenSignServer/runmigrate.js, apps/OpenSign/build/static/js/main.b9b562fb.js, apps/OpenSign/.env and .env
  4. sed -i 's#http://localhost:3000#https://your-domain.com#g' ./path-to-file for apps/OpenSign/build/static/js/main.b9b562fb.js, apps/OpenSign/.env and .env
  5. Delete the docker containers and images
  6. docker compose up -d

— Reply to this email directly, view it on GitHub https://github.com/OpenSignLabs/OpenSign/issues/647#issuecomment-2165820489, or unsubscribe https://github.com/notifications/unsubscribe-auth/A54N53XX2EIGQCIIST7ENWDZHGTH7AVCNFSM6AAAAABGZNV3WWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRVHAZDANBYHE . You are receiving this because you were mentioned.Message ID: @.***>

-- The content of this email is intended for the person or entity to which it is addressed only. This email may contain confidential information. If you are not the person to whom this message is addressed, be aware that any use, reproduction, or distribution of this message is strictly prohibited. If you received this in error, please contact the sender and immediately delete this email and any attachments.

sesscon avatar Jun 13 '24 16:06 sesscon

I wasn't able to replicate the workaround.

Steps and Actions Taken

Change API and service references in the OpenSign application from localhost to 127.0.0.1 for local development, and ensure everything functions correctly using Docker and Nginx as a reverse proxy.

Modifications Using sed: Attempted to replace http://localhost with http://127.0.0.1 in configuration files to ensure proper referencing in a local context. Specific changes included:

sed -i 's#http://localhost:8080#http://127.0.0.1:8080#g' ./apps/OpenSignServer/index.js
sed -i 's#http://localhost:3000#http://127.0.0.1:3000#g' ./apps/OpenSign/build/static/js/main.131345f3.js
sed -i 's#http://localhost:3000#http://127.0.0.1:3000#g' ./apps/OpenSign/.env

Stopped and removed the running Docker containers with:

Cleared Docker images associated with the application to eliminate any outdated versions:

docker compose down --rmi all

docker compose up -d

--

Still have the same problem

minyak1 avatar Aug 10 '24 15:08 minyak1