JQOne.Register tutorials

Start the Host on a Windows computer. Its built-in worker lets you set up a single-machine installation first.

Where to goHost console → Web dashboard → License keys

1. Run the Host. On first launch, the console waits for a valid Host license key; pressing Enter alone keeps it waiting.
2. Enter a Host license key to activate it. Save the web address, sign-in details, and node connection address shown in the console.
3. Open the web address and sign in. Under License keys → Import keys, select the correct Host or Client product type and paste one matching key per line.
4. Open Nodes and confirm that the Host's embedded worker appears. A Client is not required for a single-machine setup.

Check the resultYou can sign in and see the embedded worker on Nodes.

NoteMatch each license key to its Host or Client product type. An activation attempt with the wrong type consumes the key.

Connect other Windows computers to the Host when you need more capacity.

Where to goLicense keys → Nodes → Client console

1. Prepare a Client license key under License keys and copy the full node connection address from the Host console.
2. Run the Client on another computer. Enter its Client key, or use console option 3 to connect to the Host for a key; pressing Enter alone does not connect.
3. If the Client has no saved Host address, enter the full node connection address before starting the worker.
4. Return to Nodes and check the worker's status, last heartbeat, version, and load. Use node actions to pause new work when needed.

Check the resultThe remote worker is online and able to receive jobs.

NoteIntake paused differs from offline. Check the status and last heartbeat before troubleshooting connectivity.

A job needs at least one enabled SMS platform. Prepare proxies and other resources for the workflow you choose.

Where to goSMS platforms → Add; Proxies → Import

1. In SMS platforms, select Add, choose the provider type, enter a name, priority, and required credentials, then enable it.
2. For a rented-number provider, choose the country, project, and quantity when creating the job. A supplied-list provider uses your own numbers and code URLs.
3. Under Proxies, choose the import format and paste the proxy list. Then review the TCP and Telegram handshake test results.
4. Configure Emails, Tokens, Resource providers, Engine dictionaries, and Profile library as needed; select them in the job's advanced options.

Check the resultThe New job button is available, and the required platforms and resources can be selected in the form.

NoteNew job is unavailable until an SMS platform is enabled.

Obtain numbers from a rented-number SMS provider to create new accounts in batches.

Where to goJobs → New job → Registration

1. On Jobs, select New job, choose an enabled rented-number SMS provider, and set the job type to Registration.
2. Choose the country and project and enter the quantity. Set an operator, maximum price, or job name only if needed.
3. In advanced options, choose resource providers, client identity, and profile data. Enable @SpamBot unrestriction or tdata output if needed.
4. Submit a small quantity first. Open job details to inspect progress, failures, and workers, then increase the quantity after verifying the setup.

Check the resultThe job starts obtaining numbers, and successful accounts appear in Accounts.

NoteEnabling tdata adds a Desktop sign-in step and more processing time per account. Rented-number jobs allow up to three full attempts by default.

A supplied-list provider does not purchase numbers for you. Each line needs a number and a code URL.

Where to goJobs → New job → Supplied-list SMS platform

1. Choose an enabled supplied-list SMS platform and set the job type to Registration.
2. Enter one line per number as number|code URL|2FA password. The password is optional, and ---- can also separate fields.
3. Check numbers and code URLs before submitting. Blank lines, # comments, and duplicate numbers are skipped; malformed lines are reported separately.
4. After creating the job, inspect its details to confirm the accepted count and each number's status.

Check the resultValid lines enter the job queue; malformed lines are not counted as successful imports.

NoteThe address and number in the example are placeholders. Replace them with your working code URL and number; a number without a code URL is invalid.

Re-registration works only with a supplied-list provider and numbers that already have accounts.

Where to goJobs → New job → Supplied-list SMS platform → Re-register

1. Choose a supplied-list SMS platform, switch the job type to Re-register, and enter numbers with code URLs in the format above.
2. After the first pass, open Jobs → Items and check the bound login email, email-reset maturity time, and failure details.
3. If the result requires an email-reset cooldown, create the next pass for eligible numbers after that time.
4. Check the second pass and saved accounts. Do not treat the first pass's cooldown wait as a new-account registration success.

Check the resultJob items show each number's status; completed accounts can be checked in Accounts.

NoteRe-registration still requires a valid code URL. This job type is not available for rented-number providers.

Use Jobs to investigate failures and reconcile number usage; use Accounts to manage saved account files.

Where to goOverview → Jobs → Items / Export report → Accounts

1. Check activity in Overview, then filter Jobs and open Items for each number's status, attempts, worker, and failure reason.
2. While a job runs, inspect its live tracking log. Use Export report for successful rows, failed rows, or the raw number log.
3. After fixing resource or setting problems, use Retry failed for failed items; check cooldown times first for re-registration.
4. Open Accounts to inspect saved accounts. Import .jqo files, export selected or filtered accounts as JQO or a compatible format, and download tdata individually when present.

Check the resultYou can reconcile job items, reports, and saved accounts.

NoteThe raw number log records number acquisition for provider-bill reconciliation; it differs from account success and failure reports.

When upgrading a Host or Client, replace the program in its original installation directory and keep DataN.

Where to goStop programs → Replace program files → Restart and check

1. Stop the Host and Clients, then replace the matching program files in their original installation directories.
2. Keep the entire DataN directory, including databases, licenses, web sign-in settings, sessions, tdata, outbox, and logs.
3. Restart the Host and Clients. Check dashboard sign-in, worker status, job history, and Accounts.

Check the resultExisting jobs and accounts remain available, and the updated workers reconnect.

NoteLicensing is tied to the machine and installation path; moving to another computer or changing the path requires reactivation.