Byteweb.
Help centrePractical answers

Byteweb knowledge base

Find an answer before opening a ticket.

Quick guidance for common website, email, hosting and online-store issues. If the problem continues, the article shows what information to send us.

Website faultsMy website is unavailable

Quick checks that help Byteweb distinguish a full outage from a local connection problem.

+
  1. Open the website on mobile data or another connection.
  2. Copy the exact error message or take a screenshot.
  3. Submit an Urgent website outage ticket with the affected URL. Do not repeatedly change DNS or hosting settings.
Still need help? Create a ticket →
Website faultsA website form is not sending

Information to include when contact, enquiry or checkout notifications stop arriving.

+
  1. Submit one test using a clearly identifiable email address.
  2. Check the recipient inbox and spam folder.
  3. Send Byteweb the page URL, test time, email used and expected recipient. Never include a mailbox password.
Still need help? Create a ticket →
Content updatesPrepare a content update

A concise brief reduces clarification rounds and gets content changes scheduled faster.

+
  1. Provide the exact page URL.
  2. Paste the replacement wording and clearly label the section it replaces.
  3. Attach final images at the highest available quality and include the required deadline.
Still need help? Create a ticket →
AccessSend website access safely

Avoid sharing passwords inside ordinary ticket messages or email threads.

+
  1. Create a temporary user where the platform supports it.
  2. Grant only the access needed for the task.
  3. Tell Byteweb which platform and username are involved; use the secure access process for the password.
  4. Remove temporary access after the work is complete.
Still need help? Create a ticket →
Domains and hostingDomain or SSL warning

What to capture when visitors see a certificate, privacy or DNS warning.

+
  1. Copy the full website address from the browser.
  2. Take a screenshot that includes the warning and browser address bar.
  3. Note when the warning started and whether recent DNS or hosting changes were made.
Still need help? Create a ticket →
Domains and hostingWebsite or business email problem

The details needed to diagnose sending, receiving and website-email delivery problems.

+
  1. Confirm whether sending, receiving or both are affected.
  2. Copy the full bounce-back message without forwarding passwords.
  3. Provide the affected email address, approximate failure time and destination address.
Still need help? Create a ticket →
E-commerceE-commerce order or payment issue

How to report checkout problems without exposing customer payment information.

+
  1. Provide the order number and checkout time.
  2. Describe the payment method and visible error.
  3. Remove card numbers and sensitive payment details from screenshots before attaching them.
Still need help? Create a ticket →
Using supportChoose the right ticket priority

Urgent is reserved for outages or failures preventing customers from completing essential actions.

+
  1. Urgent: the live site is unavailable, compromised or checkout is broadly blocked.
  2. High: many users are affected but the site remains usable.
  3. Normal: standard faults, content changes and scheduled support.
  4. Low: improvements that can be handled when convenient.
Still need help? Create a ticket →