Skip to main content
Get Started

VPC Sign-in

Configure your organization's access domain to sign in to VPC services in Qoder CN.

If your organization uses VPC services, configure its access domain on the Qoder CN sign-in screen before signing in. Sign-in and model services then use the service addresses supplied by that domain.

Before you begin

  • Obtain the access domain from your organization administrator, and confirm that your network and DNS can reach the organization's VPC services.
  • Have your organization account ready. This guide uses demo.vpc.qoder.com.cn as an example; replace it with your organization's actual domain.
  • Save your work. Qoder CN restarts after you save the access domain.

Configure the access domain

1

Open access domain settings

Launch Qoder CN and click Access domain on the sign-in screen to open Configure access domain. If a domain is already configured, click the domain button showing its configured status to review or change it.
2

Enter your organization's domain

Enter the full domain provided by your administrator in Access domain. Both formats below are supported:
demo.vpc.qoder.com.cn
https://demo.vpc.qoder.com.cn
3

Save and restart

Check the domain and click Save and restart. Qoder CN restarts and uses the sign-in and model service addresses supplied by that domain. To leave without making changes, click Cancel.After restart, check that the domain button indicates a configured domain before signing in.
The configured status on the domain button means that an access domain has been set. You must still sign in with your organization account to use its services.

Sign in to your organization

1

Open your organization's sign-in page

Click Sign in in Qoder CN to open your organization's sign-in page in a browser. The application waits for browser confirmation.If the browser does not open automatically, click Copy login link and paste the link into your browser's address bar.
2

Authenticate with your enterprise account

Enter your enterprise email address, click Continue, and complete your organization's authentication flow. Use an account with access to that organization. The remaining authentication steps depend on your organization's sign-in page.
3

Return to Qoder CN and check availability

After browser authentication, return to Qoder CN and confirm that the sign-in screen has closed and the main interface is available.Create a task and send a simple request, such as “In one sentence, explain what work you can help me with.” A normal response confirms that you can proceed. Reaching the main interface confirms sign-in; receiving a task response also checks model service availability.

Change the domain or return to the public service

To connect to another organization or return to the public service, click the domain button on the sign-in screen to reopen Configure access domain.
ActionConfigurationAfter restart
Change organization domainsReplace the current domain with the new full domain, then click Save and restart.Sign in with an account for the organization associated with the new domain.
Restore the public service defaultClear the access domain, then click Save and restart.Follow the default sign-in flow.
After each change, confirm that the sign-in page and account match the intended organization, then create a task to check service availability.

Resolve connection and sign-in issues

Use the point where the flow stops to choose the next check:
SymptomSuggested action
The organization's sign-in page does not openCheck the full domain against the value provided by your administrator. Confirm that your network and DNS can reach the organization's VPC services.
The application keeps waiting for browser confirmationReturn to the browser and finish authentication. If the browser did not open, use Copy login link. To start again, click Cancel login, then sign in again.
Enterprise account authentication failsCheck that the email address belongs to the intended organization, and ask your administrator to confirm account access.
Sign-in succeeds, but tasks do not return normallySign-in and model services must both be available. Keep the error details and ask your administrator to check model service connectivity and access.