DCHost knowledge centre
Frequently asked questions
Find the answer you need to manage your service, then follow the guide for your next step.
115 answers across 8 topics
Accounts and getting started
Open the service in the customer portal and check its status, domain and access details. For hosting, use the control panel link; for a server, use the supplied connection details. Prepare your website and record existing email DNS settings before changing DNS.
The customer portal handles orders, invoices, services and support. Your hosting control panel manages files, databases and mailboxes. Access methods may differ, so use the panel link shown for your service. The customer portal itself is not a webmail application.
Payment and technical provisioning are separate steps. Check the invoice and service status in the portal. If access details are still missing, contact support with your service and invoice identifiers before placing another order. Do not include payment card details.
Include the service identifier, affected domain, time the issue began and exact error message. Describe recent changes and checks you have already made. Remove passwords, API keys and personal data from screenshots. Use customer portal support for investigations involving your account.
Open Create account in the customer portal. Enter your name, email address and a new password, then select Submit. Enter the six-digit email code on the verification screen. Email verification is part of account registration; ordering a service is a separate step.
On the sign-in screen, select Forgot password? next to the password field. Follow the recovery steps using the email address registered to your account. You do not need to create a new customer account. This recovers access to your DCHost customer account; it does not change your hosting panel or mailbox password.
Check your spam or junk folder first. If the message is still missing, use Resend Code on the verification screen and enter the newest six-digit code. Do not enter your account password in the code boxes or share the code in a support request.
Review account type, name, address and phone under Account Settings → Edit Details. Business Account shows a company-name field. Email changes use Change Email separately. Do not assume editing your profile automatically rewrites issued invoices.
Open Account Settings → Settings → Notifications and review Billing, Services, Domains and other groups separately. Save Settings and recheck your preferences. Previously sent email records are available in the account-history Emails tab.
Use Localization in the profile menu for language. Time zone is under Account Settings → Settings → General; look for Istanbul for Turkey. Records per page changes list length. The account time-zone preference does not change your server operating system.
Projects help group services for a particular task or customer. New Project walks through project details and related choices. Creating a project alone does not provision a server, pay an invoice or register a domain.
Open Audit Logs from the profile menu. Logs shows events, Emails shows sent email records, and Notifications shows portal notices. Credit Logs is for balance changes. Check search and date filters before concluding that a record is missing.
Hosting and WordPress
Choose a version supported by your application that still receives security updates. Check the versions and extensions available in your service panel. Take a backup before switching, then test the website, admin login and error logs. A PHP version change does not resolve every performance issue.
Open your hosting service in the DCHost customer portal and sign in to cPanel. Choose Install in WordPress Manager by Softaculous, then check HTTPS, the domain, installation directory and WordPress administrator details. After installation, open both the website and its dashboard. Do not start a new installation in an existing website directory.
Leave In Directory blank when WordPress should open at the main domain address and that domain’s website directory is suitable for a new installation. For a separate test installation, enter a new unused directory name; the installer creates it. Before submitting, read the full Your installation URL value and check for existing website files.
Add /wp-admin/ to your WordPress installation URL. If you installed in a subdirectory, include that same directory in the login URL. Use the WordPress administrator account you created during installation; it is separate from your DCHost customer portal and cPanel accounts.
Back up both files and the database. Confirm PHP requirements, email DNS records and the new environment’s connection settings. Test the new copy before changing DNS. For sites receiving orders or comments, plan the final data transfer and keep the old service until verification is complete.
First check that the affected post or page is published and that you are opening its correct URL. If many internal pages return 404 together, especially after migration, investigate permalinks and the server rewrite rules that handle page addresses. Record the current structure and back up .htaccess outside the web root if it exists. Then save Settings → Permalinks without changing the structure and retry the same URLs.
Record the current permalink structure and keep a copy of .htaccess outside the web root if it exists. Open Settings → Permalinks in WordPress administration; opening this screen can refresh rewrite rules. Select Save Changes without changing the selected structure, then test the existing post URLs again. If WordPress reports that .htaccess is not writable, follow the guide’s file and server checks instead of deleting the file or setting permissions to 777.
No. Redirecting every 404 URL to the homepage does not restore missing content and can send visitors to an unrelated page. If moved content has an equivalent replacement URL, redirect the old URL directly to that replacement with a permanent 301 redirect. If the content does not exist and has no suitable replacement, show a helpful 404 page and keep the missing URL’s HTTP response at 404.
WordPress cannot connect to the database that stores its site data; this message alone does not mean your data has been deleted. Note the error time and recent changes. Compare the database name, user, password and host in wp-config.php with the service configuration, then check user privileges and database service availability. Do not start a new installation or delete the existing database.
Investigate the WordPress database connection error step by step
Download wp-config.php from the correct WordPress installation first and keep the backup securely outside every website document root. DB_PASSWORD must match the current password of the database user in DB_USER, not your WordPress administrator or cPanel login password. If you change that database user’s password in cPanel, check every application that uses the same user. Correct only the confirmed mismatch, then reopen the website and WordPress administration.
Open Manage My Databases. Compare DB_NAME and DB_USER in wp-config.php with the full cPanel names, including account prefixes. Check that the user is associated with the correct database and has the privileges WordPress needs. Creating a database and a user does not automatically associate them. Opening phpMyAdmin through your cPanel session also does not prove that WordPress can connect using its own database credentials.
WordPress has encountered an error that stops execution. A failing plugin or theme, PHP incompatibility or exhausted memory can cause it; the message alone does not identify the cause. A white screen is not enough to establish the cause either. Record the error time and latest change, then check the homepage, an internal page and the administration address separately. Read the matching error log before considering a reinstall.
If you can enter recovery mode, deactivate the failing plugin in WordPress administration. If wp-admin does not open, identify the correct installation and the plugin named in the error log. Back up its files, then temporarily rename only that plugin’s directory in cPanel File Manager; do not delete it. Open /wp-admin/plugins.php (Plugins) for the same installation and confirm that the affected plugin is inactive; then retry the website. Deactivation does not fix incompatible code; test a corrected version before activating the plugin again.
Disable a failing plugin when WordPress administration is unavailable
Check the inbox and spam folder of the address used for WordPress administration notifications. A recovery mode email may not be sent for every white screen or error; delivery problems and the sending interval can also affect it. If no message arrives, use cPanel to inspect the matching error log and identify the failing component. The recovery link is private; do not include it in a support message or screenshot.
First check disk, CPU, memory and concurrent process usage around the affected times. Errors, expensive queries or plugins can also cause slowdowns. Confirm that the proposed plan increases the resource you actually need, then review the migration and billing implications.
Yes. Check its date, file and database coverage, and restoration method. A backup feature does not mean every file or recovery date is available. Keep an independent copy before important changes and, where possible, test restoration in a separate environment.
Choose Use My Domain to order hosting for a domain you already use. This is separate from a domain transfer. Check the spelling, then configure the required DNS records after hosting is ready. Review existing email records before changing DNS.
Check the order confirmation, invoice and correct service record first. Pending means this screen does not yet show the service as Active; payment and provisioning are separate stages. Recheck the status. If the record is missing or the wait is longer than expected, contact support with the order number before placing another order.
Open the correct hosting service in the customer portal and review its Access information first. cPanel Access links to the hosting panel. Your customer account and hosting panel can have separate sign-ins; do not assume one password works for both. If verification does not finish or the login page fails to load, contact support with the service number and error details.
Identify the slow operation, time, disk and resource usage first. Check the domain PHP version and application compatibility. An authorized WHM administrator can inspect PHP-FPM and OPcache. Recheck the same operation after each change instead of raising limits indiscriminately.
403 Forbidden means the server understood the request but refuses access. The status code alone does not identify the cause. Record the affected URL and time, then compare the document root, index file, file permissions and access rules with the matching error log. A security rule can also return 403.
No. Setting all files to 777 grants unnecessary write access; deleting .htaccess can remove redirects and required access restrictions. Keep a copy outside the web root first. Use the matching log and latest change to identify the cause, correct only the wrong permission or unintended rule, then retest the same URL. Appropriate permissions depend on ownership and server configuration.
Yes. A directory can return 403 when it has no file recognized as a directory index and directory listing is disabled. Compare Document Root under Domains with the folder where you uploaded the website, then check the index.php or index.html expected by your application. Do not enable directory listing to hide the problem; put the correct website files in the correct location.
A 500 error means the web server encountered an unexpected problem while completing the request. The status code alone does not identify the cause. Record the affected URL, time and latest change, then inspect the web server or PHP error log for the same time. Check whether the problem affects the whole site or only one page.
Confirm the correct domain and document root first. If you suspect an .htaccess error, compare the latest edit with the copy you saved before changing the file and read the matching log entry. Once the change is identified as the cause, reverse only that change and retest the same URL. Deleting the entire file indiscriminately can break redirects and access rules.
Record the error time and URL, then open Metrics → Errors in cPanel. Not every PHP error appears there; the PHP error log location depends on the account configuration. If you cannot find the relevant entry, contact support with the service identifier, URL, time and latest change. Remove passwords, session links and personal data before sharing log excerpts.
Backup Wizard can generate a full account backup, but restoring the complete account requires WHM or your provider. Partial file and database restores are separate. Identify the backup type and test recovery in an isolated environment without overwriting the current website.
Check the schedule, server timezone and absolute command paths. Write output to a private log outside the web root and inspect the expected time and result. A job appearing in the list does not prove execution. Remove an unnecessary one-time test job afterwards.
The module, rule package and operating mode are separate checks. Inspect rules and updates under WHM ModSecurity Vendors and Rules List, and inspect the engine in Configuration. An empty Hits List alone does not prove protection.
Domains and DNS
Yes, if the new DNS zone is missing required email records. Copy MX, SPF, DKIM, DMARC and other verification records before switching. Confirm the new zone is correct, then change the nameservers and test incoming and outgoing mail separately.
No. A domain transfer changes the registrar managing the registration; it does not move website files, databases or email. Plan hosting migration separately. Check whether the current nameservers and DNS service will remain available during the transfer. Moving hosting does not require transferring the domain.
A transfer lock, missing authorization code, domain status or registry rules may prevent it. Recent registration, transfer or certain registrant changes can also create restrictions. Check the current registrar’s status and the requirements for your extension. Never post the authorization code publicly.
No. Auto Renew sets a renewal preference. Open the domain in the customer portal and review the period, amount and payment method. When renewal is due, check both that the invoice is paid and that the domain’s Expiry Date has advanced. Insufficient credit or an incomplete payment can prevent renewal.
Change Nameserver selects the DNS provider for your domain. Register Nameserver registers a nameserver such as ns1.example.com under your own domain with an IP address. You do not need to register your own nameserver just to connect hosting or use Cloudflare. Manage A, MX and TXT records at the domain’s authoritative DNS provider.
Submitting a request does not by itself show that the domain has moved to the recipient account. Open Change Ownership for the domain again. Pending transfer approval means approval is still awaited. Active in the domain list is the registration status, which is separate from internal transfer approval. After approval, check that the domain appears in the correct account.
The transfer notification sent to your registered email links to Transfers in the customer portal. Sign in to the recipient account, review the domain and sender in the incoming requests list, and accept the request. In the Turkish screenshot these labels are Gelen transfer talepleri and Kabul Et; Reddet means Reject. Afterwards, verify that the domain appears in your account. Track requests you sent from the domain’s Change Ownership screen.
Use the device configuration or connection details in your email provider’s panel. Copy the incoming and outgoing server names, ports, encryption settings and username. Hosting your website with DCHost does not necessarily mean your email is hosted here. Check the hostname if a certificate warning appears; do not disable verification.
Sending and receiving use different settings. Check mailbox capacity, the domain’s MX records and your email provider’s service status. Send a test from an external address. If delivery fails, include the time, error code and recipient domain in a support request without sharing private message content.
Identify every service sending email for your domain. List authorized senders in one SPF record and obtain DKIM values from each relevant provider. Choose a DMARC policy after checking sending sources and authentication results. Do not copy another provider’s example values into your DNS unchanged.
Changing MX records does not migrate old messages. Create the new mailboxes and plan a separate transfer of messages and folders. Verify the new service before switching DNS. Before closing the old service, compare folders, message counts and any mail received during the transition.
A mailbox has its own password and storage quota. A forwarder routes incoming messages from an address to another destination. Creating a forwarder does not by itself create a separate mailbox. Review Email Accounts and Email Forwarding separately and check the domain’s email DNS records before expecting mail delivery.
Open Email Accounts for your hosting service. In Current Email Accounts, check the full address, domain and quota shown under Usage. The account should remain listed after refreshing the page. An increased account counter alone is not enough; test webmail access and sending and receiving separately.
Open cPanel from your hosting service. Under Email Accounts, find the correct mailbox and select Check Email on its row. On the webmail start page, Open under Open your inbox launches the Roundcube inbox. If you reach a direct sign-in screen, use your complete email address and mailbox password. This may differ from your customer portal password.
VPS, VDS and servers
Check the IP address, username, SSH port and authentication method in your service details. Verify the server’s host key through a trusted source on first connection. Do not assume that root login or a port from another example applies. Once connected, check the operating system and resources.
DCHost uses Proxmox/KVM for virtualization. This does not mean customers receive access to the physical host or its Proxmox administration panel. Check which server controls are available in your customer portal. Confirm the operating system, backup and application management included with your service.
Unmetered traffic has no per-GB/TB transfer charge and no fixed monthly transfer allowance. It does not mean unlimited connection speed or server resources. Fair Usage conditions apply. Before running sustained high-volume transfers, review the port speed, service scope and usage terms in your contract.
Review CPU load, memory, disk space, inodes and disk activity during the affected period instead of relying on one snapshot. A high load average does not always mean insufficient CPU; storage waits may contribute. Compare the findings with application logs before deciding which resource to increase.
Identify the filesystem containing the path where the error occurs. Check free space with df -hT and inode usage with df -i; do not inspect only the root filesystem. If the disk is full, identify growing directories before deleting anything. Do not remove database files or your last usable backup to make room.
Free GB does not guarantee capacity for new file records. An inode stores information about a file or directory; many small files can exhaust the available inodes. Check the affected filesystem in df -i. Identify the application producing the files and its retention policy before cleanup; do not delete entire directories indiscriminately.
If a running process still holds a deleted file open, its space may remain in use until the last open reference closes. Use lsof +L1 to inspect deleted open files and their processes. Finding a record does not mean the process should be stopped immediately. Check the application’s supported log reopen method or plan a service restart; do not terminate a live database or arbitrary processes.
Linux uses part of RAM for file cache. In free -h, inspect available memory rather than only free: available estimates memory that new applications can use without swapping. Investigate memory pressure when low available memory occurs with sustained swap activity and application slowdowns. Clearing cache indiscriminately does not fix the underlying cause.
Killed or exit code 137 alone does not prove an OOM kill; the process may have received SIGKILL for another reason. Check kernel and service logs at the incident time for Out of memory, Killed process or oom-kill records. Free RAM on the host also does not rule out a service reaching its own cgroup memory limit. Match the evidence to the process before reviewing application settings and resource limits.
Swap is disk space used for memory pages; it does not increase physical RAM. It may help absorb short peaks, but it does not by itself fix persistent RAM pressure, a memory leak or an application memory limit. Before you create swap, review existing swap, free disk space, filesystem support and workload needs. Before removing it, ensure used pages can move to RAM or other swap; never delete an active swap file directly.
No. CPU utilization shows how busy the processor is. Linux load average describes runnable tasks and tasks in uninterruptible sleep over 1, 5 and 15 minutes; it is not a CPU percentage. Review processor count, service limits and measurements from the same incident window together. High load alone does not prove that more CPU capacity is required.
Watch several top sampling intervals and sort ps output by CPU usage to identify the process name and PID. The CPU percentage in ps is an average over the process lifetime; a single row may miss a current spike. Check whether the process is an expected backup, update or scheduled scan. Being first in the list does not make it safe to terminate.
Tasks may be waiting for storage I/O; a service CPU quota or other resource limit can also cause delays. Review r, b, wa and st in vmstat alongside the incident time and application latency. I/O wait alone does not prove a disk fault, and CPU steal time alone does not establish a provider-side cause. Check memory and swap pressure before choosing a CPU upgrade.
The name resolution path could not translate the destination name into an IP address. Check the spelling and the getent ahosts result first. A failed DNS lookup does not prove that the server has lost all internet access; inspect the selected route, DNS servers and connection result separately. Identify the service managing /etc/resolv.conf before changing that file.
Separate Linux DNS failure from network and connection problems
This usually means no usable network path was found for the selected destination or address family; it does not establish a DNS fault. Inspect addresses and routes with ip -br address and ip route, then use ip route get to check the path selected for the actual destination. A default route is not always required; a specific route can be sufficient. Check IPv4 and IPv6 separately and confirm the service details before adding a gateway.
Resolving a name to an IP address does not prove that a TCP connection to the destination port can be established or that the application responds. Use curl output to identify whether the error occurs during DNS, connection, TLS or response waiting. A timeout and connection refused are different findings; a failed ping alone does not prove an internet outage either. After addressing the diagnosed cause, retry the same hostname, protocol and port and verify the expected application response.
Check the plan CPU, RAM and disk resources, location, extra IP and storage options, backup choice and operating system version. Then review the billing cycle, billing details and final total including fees. Order opens the order summary; after Check Out, verify invoice and service statuses separately.
The console opens your server’s operating-system screen. To sign in, find the username under Root Access → User on the service page, enter it at login: and press Enter. Then enter the server password at Password:. Password characters normally remain invisible. Your server and customer portal passwords may differ; use the credentials provided for the service.
No. Backup Management and Snapshot Management are separate sections. Check the allocated slots, existing records and any upgrade requirements in each section. An empty list is not evidence of a backup. Verify the scope and restore method of any copy you create.
Prepare a clean supported OS, root access, enough RAM and disk, a static public IPv4 and correct hostname DNS. After preparing AlmaLinux 9, run the official cPanel installer and complete licensing or an eligible trial in WHM. Do not install it over another panel.
Use a clean supported VPS. Prepare the OS, hostname, DNS and firewall, then run the official installer and finish initial setup and licensing. Do not install it on the same OS as cPanel. Check whether a trial is actually offered.
WHM manages the server and its hosting accounts, normally using HTTPS port 2087. cPanel manages one hosting account’s files, databases and email, normally using HTTPS port 2083. Their usernames and permissions differ.
Open a new SSH session, check the running kernel with uname -r and failed services with systemctl --failed. Confirm package completion and test your applications. An old SSH session staying open or a new kernel being installed on disk is not sufficient proof.
Adding an ISO to the portal’s image list does not install an operating system on the server’s disk. Approving partitioning or formatting in the installer can erase existing data. Check the target service and disk first, and keep a backup of the files you need outside the server.
It depends on the packages you select. Netinst is a small installation image; additional software may be downloaded from network repositories. Check the server’s IP address, subnet mask, gateway and DNS settings together with access to the package repository. When selecting options such as SSH server and standard system utilities, the installer must be able to retrieve any packages it needs.
The CD-ROM may still be the first boot device even though installation completed. Before starting partitioning again, check Templates & ISO → Boot Order in the customer portal. Put the disk containing the installed system first, choose Save, and reopen the menu to verify the selection. In the demonstration, Debian booted from disk after virtio0 was given priority.
When an ISO is attached, Templates & ISO → ISO Image opens a restart confirmation for detaching the virtual installation media. ISO Management → Delete removes the uploaded file from ISO storage. Check that operating system installation has finished, detach the ISO and verify startup from the installed disk, then delete the image if you no longer need it.
Debian and CentOS Stream support both methods. The graphical installer uses mouse-driven controls; the text-based installer uses keyboard navigation and menus. If this is your first installation, you can start by following the graphical walkthrough. Check the release, resource requirements, network information and target disk for either method.
The graphical installer is the interface used to choose settings; a desktop environment is a separate software choice. In Debian’s Software selection screen, you can deselect desktop tasks and choose SSH server and standard system utilities. In CentOS Stream, Minimal Install under Software Selection creates a system without a desktop. You then manage it through the console or SSH.
Debian graphical installation · CentOS Stream graphical installation
The official Ubuntu Server ISO used in this guide runs Subiquity’s text and menu interface. You navigate its fields with the keyboard; you do not need to perform the whole installation by typing commands. Ubuntu Desktop has a separate graphical installation workflow, not a second interface for this Server guide.
First check whether the boot options contain inst.text, which requests Anaconda’s text mode. Graphical mode also needs suitable installation media, memory and display support. A Boot ISO that retrieves packages over the network and a DVD using local installation media can have different resource requirements. Check the requirements for your installation path rather than disabling the memory check.
The x86_64 architecture label alone is not enough. CentOS Stream 10 requires x86-64-v3 CPU features, which must also be exposed to the virtual machine. Check your application’s Stream 10 support and your service’s CPU compatibility before installing from an ISO.
An LVM layout may not allocate the entire disk to the root filesystem. Filesystem capacity and volume-group space not yet assigned to a logical volume are different values. Check the root filesystem with df -h / and the group’s free space with sudo vgs. Unallocated LVM space does not mean the disk has disappeared or become smaller.
Connections and troubleshooting
A 403 points to access rules, a 404 to a missing resource, and a 500 to a server or application error. Record the time and URL, then check recent changes and relevant logs. Preserve the current state before changing permissions or reinstalling software.
For a cPanel website, follow the guide for the actual response: 403 Forbidden or 500 Internal Server Error. For missing WordPress pages, use the WordPress 404 guide.
Check that the certificate covers the hostname, is within its validity period and has a valid chain. DNS may be pointing to the wrong server. Also check mixed content and redirect loops after enabling HTTPS. Disabling certificate verification does not fix the underlying issue.
For a timeout, check the IP, port and network access. For Connection refused, check the SSH service and listening port. For Permission denied, review the username, key and permitted authentication method. Do not disable the firewall entirely; record the exact error and connection time.
Compare the database name, username, password and host in your application with the panel details. Confirm that the user has the required permissions on the correct database. Include any account prefixes added by the panel. Do not delete or overwrite the live database to troubleshoot a connection error.
Security and backups
Keep the private key on your trusted device; only the public key belongs on the server. Protect the private key with a passphrase where possible. Test a new key in a separate session before disabling an existing access method. Know how you will recover access if the key is lost.
Contact support from a trusted device and identify the affected account, symptoms and time. If you retain access, rotate passwords and relevant keys, then review active sessions and recovery details. Restoring an old backup alone does not remove the cause. Preserve evidence and never share credentials publicly.
A copy on the same server may be lost with that server. If snapshots are available, they can help recovery, but they do not replace an independent backup with a tested restore process. Define coverage for files, databases, configuration and keys, and confirm whether backup service is included.
Check the operating system version, support status and application dependencies. Prepare a current backup and recovery access, and assess whether a reboot is needed. Package updates and major version upgrades are different operations. Afterward, verify services, the application and error logs.
After signing in, open Account Settings → Change Password. Complete the current and new password fields and repeat the new password in the confirmation field. This does not change a server or hosting control-panel password.
Open Account Settings → Security → Two-Factor Auth. Complete Activate Method for an available method; opening setup alone does not enable protection. Verify the enabled status afterward. Keep the QR code, setup secret and sign-in codes private.
Contacts and Teams manage people and access. Select only the required permissions on contact or invitation forms and review billing access separately from technical service access. Department restrictions deny access, so read their description before selecting departments.
Use your public key in Public Key. Never paste the private key into a portal form or support request. Saving a key in the portal does not establish access to every existing server; verify authorization and connectivity on the server separately.
Billing and service management
Available methods appear on the relevant order or invoice screen. Check the amount, currency and billing period. If your payment provider reports success but the invoice remains unpaid, contact support with the invoice and transaction references before paying again. Do not share card numbers or verification codes.
Yes. Review the renewal date, amount and payment method in the portal. An issued invoice or saved card does not confirm a completed payment. After payment, verify both the invoice status and the service’s new expiry date. Domains and hosting may renew on different dates.
Review the plan changes offered for your service. Before confirming, check the price difference, new renewal amount and billing period. Ask whether migration, a restart or an IP change is required. If no option is shown, contact support with your service identifier and resource requirements.
Conditions can differ by service and transaction. Read the current terms and ask support to confirm eligibility for your order. Export the files, databases and email you need before the service closes. Do not assume backups or access will remain available after cancellation.
Unpaid means the invoice has not been paid. An order record does not confirm that payment was collected or that the server is ready. Check Paid and Left to pay on the invoice. If you have paid but the status has not changed, contact support with your payment reference before sending the amount again.
Open Billing → Add Funds. Choose an amount and method, then compare the credit, fee and total. Complete payment for the invoice created after Add Funds Securely. Check Available Credit and Credit Logs afterward. Creating an invoice alone does not add usable credit.
Open View for the invoice under Billing → Invoice Management. Check the service, total and deadline, then select a method with Pay Now. After completing provider checkout, verify the invoice status and Left to pay in the portal. Do not immediately repeat a bank-confirmed payment because the portal has not updated.
Open the Billing tab in Billing Settings. It includes the default gateway, automatic credit use, delivery preference and invoice merging. Company and address details belong under Edit Details. Reopen the screen after saving to verify the preferences persisted.
Saving a card and enabling automatic charging are separate. Check Saved Cards and Auto Charge on Payment Methods, plus the preferences offered under Auto-Pay Setup. Saving information with Link during external checkout is also separate from portal automatic-payment settings.
If Auto-apply credit is enabled, credit may be applied to new orders or recurring invoices. Read Decrease, Credit After and Related Invoice together in Credit Logs. Review the result before repeating a top-up and ask support about unexplained entries.
Merged means the invoice was combined into another invoice, not paid. Follow the new invoice number and review its status, services, total and deadline. Pay all due invoices may create a combined invoice.
Account Statement in Billing Center downloads a PDF statement; check browser downloads if the page stays unchanged. Use Download PDF on an invoice for that document, or select invoice rows and use Download Selected for multiple files.
Open the invoice and choose Pay Now, then select Credit Balance. Check the updated total before submitting once. Wait for the result, then compare the invoice status, Left to pay and your account balance.
An amount on the Credit line can mean account credit covers the order. Read Subtotal, Credit, Total Recurring and Total Due Today together, then check your remaining credit after checkout. No external payment being due today does not make future service periods free.
Share the details of your issue
The service, error message and time help us investigate.