Issue: Delayed Access and Login Problems After Deployment on Oracle Cloud #7286

Closed
opened 2026-02-21 18:19:49 -05:00 by yindo · 3 comments
Owner

Originally created by @lukefan on GitHub (Dec 19, 2024).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.14.0

Cloud or Self Hosted

Cloud

Steps to reproduce

Description: I have deployed Dify locally without any issues—browsing the site works as expected. However, after deploying Dify on Oracle Cloud, a strange issue occurs:

When accessing the site on MacOS (using Chrome), after a while, I am unable to access the site. It takes a long time to redirect to /signin, where I need to log in again.
After logging in, everything works fine. But if I leave the site idle for an extended period, the site automatically redirects to /app, and then after a long wait, it redirects to /signin again for re-login.
A workaround is to manually enter /signin to avoid waiting for the long delay.
However, when accessing the site on Windows 11 (using Chrome), there are no such issues. The site automatically redirects to /app and doesn't require a new login, even after days of inactivity.

Expected Behavior: I hope the system can be adjusted so that if login fails, it can quickly redirect to /signin to allow re-login, without causing unnecessary waiting.

Steps to Reproduce:

Deploy Dify on Oracle Cloud.
Access the site using Chrome on MacOS.
Wait for a while (leave idle or inactive for some time).
Attempt to access any page (it will either take too long to redirect to /signin or the site will remain unresponsive).
Log in through /signin, and everything works fine again.
Additional Context:

MacOS (Chrome): Delayed login, redirects to /signin after inactivity.
Windows 11 (Chrome): No issue, redirects to /app without requiring re-login.
Possible Fix:

Ensure that the site quickly redirects to /signin when login fails, so users can re-login without unnecessary delay.

✔️ Expected Behavior

I don't need to log in. I can directly enter the /app path and start working.
If I need to log in again, I can quickly jump to the /signin path to log in.

Actual Behavior

Under the /app website, it took a long time. Only after several minutes did it jump to the /signin path to log in.

Originally created by @lukefan on GitHub (Dec 19, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.14.0 ### Cloud or Self Hosted Cloud ### Steps to reproduce Description: I have deployed Dify locally without any issues—browsing the site works as expected. However, after deploying Dify on Oracle Cloud, a strange issue occurs: When accessing the site on MacOS (using Chrome), after a while, I am unable to access the site. It takes a long time to redirect to /signin, where I need to log in again. After logging in, everything works fine. But if I leave the site idle for an extended period, the site automatically redirects to /app, and then after a long wait, it redirects to /signin again for re-login. A workaround is to manually enter /signin to avoid waiting for the long delay. However, when accessing the site on Windows 11 (using Chrome), there are no such issues. The site automatically redirects to /app and doesn't require a new login, even after days of inactivity. Expected Behavior: I hope the system can be adjusted so that if login fails, it can quickly redirect to /signin to allow re-login, without causing unnecessary waiting. Steps to Reproduce: Deploy Dify on Oracle Cloud. Access the site using Chrome on MacOS. Wait for a while (leave idle or inactive for some time). Attempt to access any page (it will either take too long to redirect to /signin or the site will remain unresponsive). Log in through /signin, and everything works fine again. Additional Context: MacOS (Chrome): Delayed login, redirects to /signin after inactivity. Windows 11 (Chrome): No issue, redirects to /app without requiring re-login. Possible Fix: Ensure that the site quickly redirects to /signin when login fails, so users can re-login without unnecessary delay. ### ✔️ Expected Behavior I don't need to log in. I can directly enter the /app path and start working. If I need to log in again, I can quickly jump to the /signin path to log in. ### ❌ Actual Behavior Under the /app website, it took a long time. Only after several minutes did it jump to the /signin path to log in.
yindo added the 🐞 bugcloud labels 2026-02-21 18:19:49 -05:00
yindo closed this issue 2026-02-21 18:19:49 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Jan 20, 2025):

Hi, @lukefan. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary

  • Users face delayed access and login issues on Dify using MacOS with Chrome on Oracle Cloud.
  • The problem does not occur on Windows 11 with Chrome.
  • Suggestion to implement quicker redirection to the login page.
  • No further comments or developments have been made.

Next Steps

  • Please confirm if this issue is still relevant with the latest version of Dify.
  • If there is no response, the issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 20, 2025): Hi, @lukefan. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary** - Users face delayed access and login issues on Dify using MacOS with Chrome on Oracle Cloud. - The problem does not occur on Windows 11 with Chrome. - Suggestion to implement quicker redirection to the login page. - No further comments or developments have been made. **Next Steps** - Please confirm if this issue is still relevant with the latest version of Dify. - If there is no response, the issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
Author
Owner

@lukefan commented on GitHub (Jan 20, 2025):

Hi, @lukefan. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary

  • Users face delayed access and login issues on Dify using MacOS with Chrome on Oracle Cloud.
  • The problem does not occur on Windows 11 with Chrome.
  • Suggestion to implement quicker redirection to the login page.
  • No further comments or developments have been made.

Next Steps

  • Please confirm if this issue is still relevant with the latest version of Dify.
  • If there is no response, the issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

The problem was solved after version 0.15.1.
thanks.

@lukefan commented on GitHub (Jan 20, 2025): > Hi, [@lukefan](https://github.com/lukefan). I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. > > **Issue Summary** > > * Users face delayed access and login issues on Dify using MacOS with Chrome on Oracle Cloud. > * The problem does not occur on Windows 11 with Chrome. > * Suggestion to implement quicker redirection to the login page. > * No further comments or developments have been made. > > **Next Steps** > > * Please confirm if this issue is still relevant with the latest version of Dify. > * If there is no response, the issue will be automatically closed in 15 days. > > Thank you for your understanding and contribution! The problem was solved after version 0.15.1. thanks.
Author
Owner

@dosubot[bot] commented on GitHub (Jan 20, 2025):

Thank you for closing the issue, lukefan! We appreciate your contribution to Dify.

@dosubot[bot] commented on GitHub (Jan 20, 2025): Thank you for closing the issue, lukefan! We appreciate your contribution to Dify.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#7286