Own Ebook Customer Portal

Support

Documentation · Own Ebook self-hosted

Contact support@ownebook.com from your purchase email address. Include your order reference, installed version, domain, hosting provider/panel, step and the non-secret error message.

Do not send passwords, Setup keys, license keys, database URIs or AI/payment credentials. Your purchaser account manages software licenses; your installed workspace manages its own users.

Technical appendix for hosting providers

This appendix is for the provider maintaining an individual account/domain. It is not a set of root commands for a buyer, and it does not authorize global changes to shared web-server settings or automatic quota/plan upgrades. Confirm the actual panel: the illustrated Hostbas link says “Login to cPanel”, but the screenshots show Webuzo.

Private application path and the installer hand-off

Keep the full package at /home/YOUR_USER/ownebook with start.cjs inside. Never serve the application source from public_html, an add-on domain’s DocumentRoot or any other public directory. In the reviewed myaton.shop account, /home/atonboxs/myaton.shop is the public DocumentRoot and /home/atonboxs/ownebook is the private application source; only routing configuration belongs in the public folder. Try Ebook’s public_html extraction procedure does not apply.

If you prepare the runtime, give the owner the HTTPS installer URL and private Setup key. The owner proceeds directly in the browser, without another upload or Node.js application. Keep Setup key separate from the owner’s Gumroad license key. Otherwise, confirm suitable Node.js and Application Manager before the owner follows the self-managed steps.

CageFS working directory

On the reviewed Hostbas server, a read-only check found that the inherited working directory could become inaccessible after CageFS entry: os.getcwd() raised PermissionError even when the pre-entry directory was inside the account. Changing into the private application directory after lve_wrapper succeeds. Both generated start and stop commands therefore enter /bin/bash through the wrapper and run cd there before exec Node.

Use the validated command generator for this Hostbas configuration. Its /usr/bin/lve_wrapper and /opt/own-ebook-node/bin/node paths are provider-specific. Another provider must confirm its own Node path and isolation mechanism. Validate the result in Application Manager on a test account and run the browser’s Check requirements before adopting new operational screenshots.

When Webuzo changes command quotes

The 12 November test on the existing oebooklab account found that this Webuzo installation added backslashes to quotes when saving the start/stop fields. The command pasted directly into those fields did not start the installer. Do not treat a “command issued successfully” message as proof of a running application; inspect its status and HTTPS response.

The provider can keep the exact generated commands in two private, account-owned shell files, outside every DocumentRoot, with mode 600. For example, create /home/YOUR_USER/ownebook-start.sh containing #!/bin/bash on its first line and the generated start command on its next line. Create /home/YOUR_USER/ownebook-stop.sh the same way with the generated stop command. Replace YOUR_USER with the verified account name, use the panel-assigned port in the generated start command, and keep cd inside the lve_wrapper /bin/bash -c program. Do not edit a signed ZIP or copy secrets into these files.

Use these simple paths in the same Application Manager application:

Start Command: /bin/bash /home/YOUR_USER/ownebook-start.sh
Stop Command:  /bin/bash /home/YOUR_USER/ownebook-stop.sh

This private-script route ran the exact generated commands through Application Manager and passed the browser’s Check requirements on the unchanged 1.0.14 full package with Node.js 24.22.2. It does not establish that the quoted command fields work directly on this panel. No Atlas credentials, customer-license activation or administrator creation were submitted in that test. Keep the existing screenshots labelled as historical field examples; do not present them as verification of the corrected command fields.

Atlas egress and DNS

Measure the application’s actual public egress IP from its account environment; do not infer it from the domain A record or Shared IP. Have the owner allow it in Atlas as /32 for a single IPv4. Separately permit outbound TCP 27017 to Atlas nodes with DNS/SRV working. No inbound MongoDB port is required on the web server. Keep TLS verification enabled. MongoDB reference.

The measured 63.250.32.101/32 value is a myaton.shop example only. Its account-specific provider service reads the Atlas hostname supplied by the owner and allows only its nodes’ public addresses. This service is not a feature promised in every distributed copy. Add Current IP Address is optional for a purchaser using local database tools; it must not remove the hosting egress entry.

Chromium, fonts and PDF acceptance

Check Chromium’s system dependencies and the font files visible to the application inside CageFS. Cached fc-list names are insufficient evidence that the referenced files can be read. In the myaton case, adding freely licensed DejaVu fonts and their license inside the account resolved squares in the PDF. Validate the actual Arabic and English glyphs in an opened PDF, not only successful generation or byte count. Keep account limits unchanged.

Restart after setup and older-version updates

The general 1.0.14 browser-installer flow still requests Stop/Start of its Application Manager application after completion. If you provide a confirmed automatic restart controller, tell the owner to wait for readiness and then open /login. The myaton provider controller switches from installer to application automatically; the owner must not create or restart another application.

Fresh 1.0.14+ installations include admin updating at Admin → License & Updates. Older installations need one manual update and a restart of the same controller. Shared-hosting users must not run the VPS enable-admin-updates.py command. Keep a manual recovery path, preserve interrupted installation state and maintain off-host database/files backups.

LiteSpeed: diagnose 421 and 426 per domain

  • Preserve the original public Host when proxying to the loopback application; do not send 127.0.0.1 as the host.
  • Forward one trusted X-Forwarded-Proto: https value for the HTTPS request. Avoid duplicate RequestHeader rules producing https, https; verify what the application receives.
  • Redirect HTTP and the www alias to the configured canonical HTTPS URL. Retain a working /.well-known/ exception for certificate renewal rather than sending that path into the application.
  • Apply and verify the correction in the affected domain’s include, respecting the provider’s supported proxy configuration. Do not alter central shared LiteSpeed settings for all sites.

In the reviewed myaton configuration, Rewrite proxying to 127.0.0.1 changed Host to an IP, and repeated RequestHeader directives produced “https, https”. A domain-specific include using ProxyPassMatch and ProxyPreserveHost resolved that case without editing central LiteSpeed settings. Treat this as case evidence, not a universal include to paste into every provider’s configuration. See LiteSpeed’s reverse-proxy documentation.

Scope of the 12 November review

The supplied myaton review covered the installer screen, hosting check, session protection and readable Arabic/English PDF output. Atlas entry, customer-license activation and administrator creation were left to the owner. Do not record those as completed before the owner performs them. Historical lab screenshots and older release numbers are examples, not evidence of this customer’s activation.

Resource exhaustion and recovery in 1.0.15

Use one API process per installation. The limited shared-hosting profile defaults to one generation job, one export, one PDF job and one Chromium browser, with four waiting PDF jobs. PDF queue wait is 60 seconds and the total job deadline is 180 seconds, both configurable through the private backend environment. Details and allowed values are in resources/shared-hosting-resources.md inside the signed package. Explicit valid existing overrides remain respected.

The controller defaults to a 300-second startup deadline and three total starts in a 900-second window, with backoff and ongoing readiness checks. Put controller settings in the hosting manager environment, not only backend.env. After exhaustion it closes the gateway and exits nonzero; configure bounded manager retries and inspect memory/process quota events. A 1 GB / 100-process quota has failed under load; this release does not certify small-account capacity or raise limits. Test actual peak usage inside the customer's isolation.

After a successful 1.0.14 → 1.0.15 update, Stop/Start the same controller once to load the new runtime. Never do this while an update or restore is running. The private maintenance marker and update/restore locks prevent unintended startup. Restore to a new empty database, preserve failed-operation reports, and explicitly resume only after verification. Paid AI operations with unknown outcomes are left for review, with completed pages and approved budget snapshots preserved.

Release validation used isolated process fault injection, concurrent real Chromium exports and database fixtures. It was not a new load or activation test inside the myaton customer account.

Verified controller restart guidance in 1.0.16

The shared controller reports a code fingerprint captured once at process startup. The API compares it with the installed controller files, not just the release version. Older controllers that do not report it require one restart after a successful update. The admin reminder stays until a matching controller is ready; failed status requests never confirm completion.

Stop/Start instructions are withheld during running updates, update/restore locks, intentional maintenance and incomplete recovery. Review the operation rather than deleting locks. “Check restart status” is read-only. Application-only updates with unchanged controller code do not require a hosting restart. No extra restart is needed on a fresh 1.0.16 installation after its normal startup.

Support: saved PDF recovery in 1.0.17

Check saved PDF uses the existing content and assets. The source, layout, asset bytes and rendering engine are fingerprinted; a database lease and source-version checks prevent a stale result from replacing a customer edit. Review any unresolved provider outcome before another paid request. Keep existing settlement, Pro, Designer, Premium and Composition approvals in force.

The packaged backend/scripts/repair-pdf-state.cjs defaults to dry-run. Reports classify stale warnings, identical adjacent QA copies, actual overflow, conflicting manuscripts and missing content/assets. Apply only an explicitly reviewed book, with a private backup outside every DocumentRoot. Differing summaries and instructions are retained. No historical ledger entry or automatic refund is changed. Read resources/pdf-recovery.md before using the tool.

A provider-specific 1.0.16 guard is not shipped in the general package. The hosting operator must validate 1.0.17 on an isolated fixture, preserve the previous setup and test rollback before removing that guard. The myaton original and its two conflicting drafts must remain untouched pending the owner's decision. This release's automated checks do not constitute installation or activation on that customer account.

Interrupted Pro preparation in 1.0.19

Open View Pro progress on the existing book. Finished text, the cover and delivered Pro pages stay saved. Before an AI operation begins, temporary database/PDF failures wait with bounded retries. Repeated failures pause with a reason and one attention notification. A temporary HTTP 503 is not evidence that a book was deleted; do not create the same book again.

Continue processes only remaining selected pages under the existing approval, available balance and spending limits; new AI work can use that balance. It does not re-charge finished pages. Uncertain provider results require reconciliation, not automatic replay. Updating does not resume previously paused or cancelled selections. A free Check saved PDF is separate from producing new Pro artwork.

All PDF paths share bounded renderer capacity. For limited hosting use OWN_EBOOK_RESOURCE_PROFILE=limited and validate actual Arabic/English PDFs. Check database DNS/outbound connectivity and hosting resource logs if failures persist. Do not infer out-of-memory from a generic error or increase account limits automatically. See resources/pro-recovery.md in the package.