## What this teaches
How to local proxy errors when not signed in are warnings now, not crashes (apify 3.1.15+).
## The problem
Issue apify/apify-sdk-js#262 (closed, 4 comments): The request was to change Actor.createProxyConfiguration so it no longer throws when a user is not logged in or lacks Apify Proxy access. Throwing forced every new local user into two confusing errors: access denied, sign in required. Maintainers agreed the local behavior should just print a warning and skip proxy usage when APIFY_IS_AT_HOME is not set, keeping proxy-on for consistency where it is available. The change shipped in apify 3.1.15 and the maintainer verified it against a fresh Playwright template.
## What worked (verified answer)
If you are running an Actor template locally and Actor.createProxyConfiguration blows up with access denied or sign in required errors, upgrade to apify 3.1.15 or later. Since that release the SDK prints a visible warning instead of throwing when you are not signed in or lack proxy access, so templates run locally without forcing you to log in first. This only changes the local path. On the platform the proxy still applies, which keeps local behavior consistent with production. If you do want the proxy locally, run apify login to get the proxy password and the warning goes away.
## Source
gh:apify/apify-sdk-js#262 - https://github.com/apify/apify-sdk-js/issues/262