dify - ✅(Solved) Fix allow configurable Next.js dev origins [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35682Fetched 2026-04-30 06:45:41
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
1
Author
Participants
Timeline (top)
closed ×1cross-referenced ×1labeled ×1

Fix Action

Fixed

PR fix notes

PR #35683: chore: allow configurable Next.js dev origins

Description (problem / solution / changelog)

[!IMPORTANT]

  1. Make sure you have read our contribution guidelines
  2. Ensure there is an associated issue and you have been assigned to it
  3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

<!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. --> <!-- If this PR was created by an automated agent, add `From <Tool Name>` as the final line of the description. Example: `From Codex`. -->

fix https://github.com/langgenius/dify/issues/35682

NEXT_ALLOWED_DEV_ORIGINS=100.116.66.123

Screenshots

BeforeAfter
......

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran make lint && make type-check (backend) and cd web && pnpm exec vp staged (frontend) to appease the lint gods

Changed files

  • web/next.config.ts (modified, +4/-0)
RAW_BUFFERClick to expand / collapse

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Allow configuring Next.js development allowed origins through an environment variable.

This is useful for remote development scenarios where the dev server is accessed through a LAN, VPN, or IP instead of localhost.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.

extent analysis

TL;DR

Configure Next.js development allowed origins using an environment variable to enable remote development scenarios.

Guidance

  • Review the Next.js documentation to determine the specific environment variable that controls allowed origins.
  • Investigate how to set environment variables in your development environment, such as using a .env file or command-line arguments.
  • Consider the security implications of allowing remote access to your development server and ensure proper authentication and authorization mechanisms are in place.
  • Research existing solutions or issues in the Next.js community that may have already addressed this feature request.

Notes

The implementation details may vary depending on the specific Next.js version and development setup being used.

Recommendation

Apply workaround by configuring the environment variable as described in the Next.js documentation, allowing for more flexible development scenarios.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

dify - ✅(Solved) Fix allow configurable Next.js dev origins [1 pull requests, 1 participants]