Skip to content

fix: keep --remote running when public IPv4 lookup fails - #2725

Open
BetterAndBetterII wants to merge 1 commit into
slidevjs:mainfrom
BetterAndBetterII:fix/public-ipv4-error-handling
Open

fix: keep --remote running when public IPv4 lookup fails#2725
BetterAndBetterII wants to merge 1 commit into
slidevjs:mainfrom
BetterAndBetterII:fix/public-ipv4-error-handling

Conversation

@BetterAndBetterII

Copy link
Copy Markdown

public-ip publicIpv4() throws when the public address cannot be determined (blocked DNS, DOMException in practice). Both --remote startup and the QR shortcut awaited it unguarded, so slidev --remote= crashed instead of staying on LAN URLs.

Catch the lookup and treat failure as no public IP. printInfo already omits that line when the value is missing, so remote/QR keep working.

Fixes #2724

publicIpv4() throws (for example DOMException when DNS is blocked),
which crashed the CLI on --remote=password and the QR shortcut.
@netlify

netlify Bot commented Aug 26, 2026

Copy link
Copy Markdown

Deploy Preview for slidev ready!

Name Link
🔨 Latest commit ad43795
🔍 Latest deploy log https://app.netlify.com/projects/slidev/deploys/6a8ef4c55f1d3c0008e71b4d
😎 Deploy Preview https://deploy-preview-2725--slidev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add error handling for calls to publicIpv4 to prevent crashing on --remote=<password> if public IP cannot be determined.

1 participant