[howwohmm]

Fixes #2642

Problem
signOut({ redirect: false }) returns an absolute URL built from NEXTAUTH_URL (e.g. http://localhost:3000/). When Docker remaps an external port to the container's internal port, the redirect sends users to the wrong port instead of the one they're actually on.

Fix
Replace router.push(d.url) with router.push("/") in apps/web/app/logout/page.tsx. The returned d.url is no longer needed — Next.js resolves relative paths against the user's current origin, so the port is always correct. The signOut call itself is unchanged; only the subsequent client redirect changes.

What this doesn't change
Session termination, the callbackUrl: "/" option, or any server-side auth behavior — this is purely a client-side redirect fix.

[coderabbitai]

Walkthrough

The logout page control flow has been updated to navigate to a fixed root path ("/") after sign-out completes, instead of using the dynamic URL returned from the signOut callback. The clearHistory() function is invoked before the redirect.

Changes

Cohort / File(s)	Summary
Logout Navigation Logic apps/web/app/logout/page.tsx	Modified the .then callback in the sign-out flow to redirect to a fixed "/" path instead of the returned d.url value. Removed the resolved value parameter and reordered clearHistory() execution before redirect.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: replacing an absolute URL redirect with a relative path to fix port mismatches in Docker environments.
Description check	✅ Passed	The description comprehensively explains the problem (Docker port remapping causing wrong redirects), the solution (using relative paths), and what remains unchanged (session termination and server-side auth).

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Greptile Summary

This PR fixes a client-side redirect bug where users in Docker environments with remapped ports were sent to the wrong port after logout. The fix replaces router.push(d.url) (where d.url is an absolute URL derived from NEXTAUTH_URL) with router.push("/"), so Next.js resolves the redirect against the user's current origin — always using the correct port.

• Root cause: signOut({ redirect: false }) returns { url } built from NEXTAUTH_URL, which may point to the container's internal port rather than the externally-mapped port
• Fix: Use router.push("/") so the redirect is relative and always resolves to the user's current origin
• Note: callbackUrl: "/" passed to signOut is now effectively unused since d.url is never consumed, but it is harmless to keep in place
• No server-side auth behavior, session termination logic, or other functionality is affected

Confidence Score: 5/5

This PR is safe to merge — it is a targeted, low-risk fix for a well-described client-side redirect bug.

The change is a single-line fix replacing an absolute URL (potentially wrong port) with a relative path (always correct). No logic, security, or data-integrity concerns are introduced.

No files require special attention.

Important Files Changed

Filename	Overview
apps/web/app/logout/page.tsx	Replaces absolute URL redirect from signOut return value with relative path / to fix port mismatch in Docker environments

_{Reviews (1): Last reviewed commit: "fix: use relative path for logout redire..." | Re-trigger Greptile}

[coderabbitai]

🧹 Nitpick comments (1)

apps/web/app/logout/page.tsx (1)

20-23: Await clearHistory() before navigating to ensure cleanup completes

clearHistory() is async but called without await on line 21. The router.push("/") on line 22 executes immediately, creating a race where search history cleanup may finish after navigation completes.

Proposed fix

 useEffect(() => {
-  signOut({
-    redirect: false,
-    callbackUrl: "/",
-  }).then(() => {
-    clearHistory();
-    router.push("/");
-  });
+  const runLogout = async () => {
+    await signOut({
+      redirect: false,
+      callbackUrl: "/",
+    });
+    await clearHistory();
+    router.push("/");
+  };
+  void runLogout();
 }, []);

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@apps/web/app/logout/page.tsx` around lines 20 - 23, The promise chain calls
clearHistory() without awaiting it, causing router.push("/") to run before
cleanup completes; update the .then callback (or make the surrounding handler
async) to await clearHistory() before calling router.push("/") so history
cleanup finishes prior to navigation (use await clearHistory(); router.push("/")
or return clearHistory().then(() => router.push("/")) in the promise chain).

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@apps/web/app/logout/page.tsx`:
- Around line 20-23: The promise chain calls clearHistory() without awaiting it,
causing router.push("/") to run before cleanup completes; update the .then
callback (or make the surrounding handler async) to await clearHistory() before
calling router.push("/") so history cleanup finishes prior to navigation (use
await clearHistory(); router.push("/") or return clearHistory().then(() =>
router.push("/")) in the promise chain).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a16e9439-4fa1-477e-91dd-44552bb6b56e

📥 Commits

Reviewing files that changed from the base of the PR and between bc14214 and 9c89253.

📒 Files selected for processing (1)

• apps/web/app/logout/page.tsx

[MohamedBassem]

Thank you