openimsdk / openimsdk/openim-docker

[BUG] Deploying using source code, configuring Nginx for domain access, and the issue of the front-end code hardcoding the port number.

Open
#259 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go Template
Stars
88
Forks
114
PR merge metrics
No merged PRs in 30d

Description

OpenIM Server Version

3.8.2,3.8.3

Operating System and CPU Architecture

Linux (AMD)

Deployment Method

Source Code Deployment

Bug Description and Steps to Reproduce
Image After deploying using the source code method, both the server and chat started normally. The domain name was configured according to the Nginx template in the official documentation. Accessing via the domain name displays the login page, but after clicking login, it was found that the requests to the backend still include the port number, resulting in failure to properly reach the backend.
Screenshots Link

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Nginx template in the official documentation and the frontend configuration used during source-code deployment. Reproduce domain access through Nginx and inspect the backend requests after login. Done means the requests no longer include an unreachable backend port and login reaches the backend successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
nginx
Domain
devops, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.