Find an answer. Resolve the issue.

Confirm that you are using the email connected to the account and check that Caps Lock or a password manager has not changed the password. Try the reset-password page and a private browser window. If the problem continues, send the account email and the exact message shown; never send your password.

Check the hostname, port, protocol, username, password, and selected plan. Confirm that the plan is active and that your client supports HTTP(S) or SOCKS5 as configured. Retry one request to a simple public page, then contact support with the time, timezone, product, and a redacted connection example.

Review the selected country, state or city where available, and confirm whether the request uses a rotating or persistent session. Persistent sessions can still change when their session window ends or network availability changes. Include the requested location and session type in your support request.

Confirm the target URL is public, review the request options, and retry with a smaller item limit. Check Crawler Logs for the task status and error details. Send the task ID, target domain, expected output, actual result, and approximate time without including private credentials.

Confirm that the MCP key is active, the client configuration uses the Arcvenza Streamable HTTP endpoint, and the authorization header contains the complete key. Save the configuration and fully restart the AI client. Do not use the legacy SSE transport.

Use the Base URL and private gateway key shown in the Dashboard, and copy an available model identifier exactly. A regenerated key immediately invalidates the previous key. Confirm that the account has available gateway credit before retrying.

Residential and Mobile plans use traffic, ISP and Datacenter plans use allocated IPs, Unlimited Residential uses an access window and bandwidth tier, and Crawler Console uses package calls and concurrency. Review the selected plan and Order History before reporting an incorrect total.

Open My Subscriptions in the Dashboard, open the plan's Action menu, and choose Cancel subscription. Cancellation stops the next renewal but does not end the current paid access immediately or reverse a completed payment. The service remains available until its listed expiry, subject to plan limits.

Check Network Status first. If no incident is listed, retry from another local connection and record the product, endpoint, time with timezone, and any request or task ID. Avoid repeated high-volume retries while an issue is being investigated.

Refresh Order History and the matching product workspace after payment confirmation. Make sure you are signed in to the account used at checkout. If the order is marked paid but access is still missing, send the order ID, product, payment time, and account email to support. Do not send full card or payment credentials.

Copy the current credentials from the active plan rather than reusing an older saved configuration. Check for extra spaces, confirm the correct endpoint and port, and verify that the selected protocol is supported by the client. If credentials were exposed, replace or regenerate them before testing again.

Pause the application and review traffic history by time and plan. Check retry loops, parallel workers, large media responses, and applications sharing the same credentials. Compare one controlled request with its response size, then contact support with the plan ID and time range if the total still looks incorrect.

Persistent sessions are designed to keep an IP within the available session window, but they are not permanent assignments. Reuse the same session identifier and endpoint, avoid switching locations mid-session, and check whether the session duration ended. Network availability may also require an IP change.

Test the assigned IP against a simple public page first, then confirm whether the issue affects one target or all destinations. Review the target's access rules and your request rate. Send the plan ID, redacted IP, protocol, target domain, and timestamp to support; do not attempt to bypass access controls.

Confirm the plan is active and compare the workload with the selected bandwidth tier. Reduce simultaneous transfers, large downloads, and retry loops, then test one request from a stable local connection. Include the plan ID, bandwidth tier, concurrency, and time range when requesting help.

A task needs an available package call, and each running task occupies a concurrency slot. Wait for active tasks to finish or stop work that is no longer needed. Review the package balance before retrying; repeated retries can consume additional calls when new tasks start successfully.

Create a new MCP key in the Web MCP workspace, choose an appropriate expiry, and replace the old token in the client configuration. Save the file and fully restart the client. Revoked or expired keys cannot be restored, and the full replacement key should never be committed to a repository.

Confirm that the AI Model Gateway is active, the account has available gateway credit, and the selected model is still listed as available. Refresh the page and retry a short prompt. If it still fails, include the model, time, displayed error, and a redacted screenshot in the support request.

Compare the amount, product, order ID, and timestamp in Order History before contacting support. Pending card authorizations may not be completed charges. Send the relevant order IDs and a redacted payment record; do not include a full card number, security code, or banking password.

Stop using the affected credential immediately. Regenerate or revoke the key from the relevant Dashboard workspace, update trusted clients, and remove it from messages, screenshots, logs, and repositories. Contact support promptly with the product and approximate exposure time, but never include the exposed secret itself.

Include the account email, affected product and plan, order or task ID when available, the time with timezone, steps to reproduce, expected behavior, actual result, and a redacted screenshot or connection sample. Never include passwords, private keys, full proxy credentials, or payment-card details.