FQDN WAN IP in server detail did not update
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 113
- Forks
- 22
- Avg merge
- 10h 40m
- Merged PRs (30d)
- 13
Description
Environment
Unraid OS Version:
7.2.2
Are you using a reverse proxy?
Yes, but I do not think it is related.
Pre-submission Checklist
- I have verified that my Unraid OS is up to date
- I have tested this issue by accessing my server directly (not through a reverse proxy)
- This is not an Unraid Connect related issue (if it is, please submit via the support form instead)
Issue Description
My WAN IP changes every week.
FQDN WAN IP in server detail did not update to correct WAN IP, it is still point to old WAN IP untail I manually sign out/sign in. Restart API did not update WAN IP as well.
Steps to Reproduce
The issue happens for a while.
Allow Remote Access: Always
Remote Access Forward Type: Static
Expected Behavior
Check current WAN IP and update to connect.myunraid.net
Actual Behavior
WAN IP did not update.
Additional Context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Start by reproducing the problem with Allow Remote Access set to Always and Remote Access Forward Type set to Static, then trace the API path supplying the FQDN WAN IP in server details. Done means a changed WAN IP is reflected without signing out and back in or restarting the API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100