Troubleshooting

Resolve common Linkyhost sign-in, upload, website, link, analytics, password, team, custom-domain, and API problems.

Start with these checks

Copy the exact error before refreshing.
Confirm you are signed in and in the intended Personal or team workspace.
Check the file against Limits.
Retry once in a current browser with extensions that alter uploads disabled.
Test a published URL in a private window.

Upload problems

Message or symptom	Likely cause	What to do
Unsupported file type	The standard uploader does not accept the extension or reported content	Use PDF, DOCX, HTML, TXT/CSV, supported image, or a website ZIP
File type does not match	The bytes do not match the extension or browser type	Re-export the original file; do not rename its extension
File is too large	It exceeds the workspace plan	Reduce the file or use a plan with a higher 10/100/500 MB limit
Upload limit reached	The Free workspace already has a link or the user-wide ceiling was reached	Delete an unneeded link or change plan as applicable
Address unavailable	The requested Linkyhost address is claimed or reserved	Choose a different address
Upload rejected	Publication or content-policy checks did not pass	Review the error and the Terms; use a legitimate clean source file
Stuck on Processing	A publication check has not finished	Wait briefly and reload; contact support if it persists

Keep the tab open until publication completes. If the connection fails during transfer, retry from the original file rather than a partially downloaded copy.

Website ZIP problems

Symptom	Fix
“No usable HTML page”	Put `index.html` at the archive root or include another valid HTML entry page
Source tree detected / build output missing	Run the framework's static build locally and ZIP `dist`, `out`, `build`, or the generated output contents
ZIP requires Pro	Multi-file website bundles are Pro; upload one constrained standalone HTML page on Free instead
Entry or unpacked-size limit	Reduce below 5,000 entries and 200 MB declared uncompressed size
CSS/images/scripts return 404	Fix relative paths, filename case, and the ZIP root; include every required asset
SPA works from Home but not after refresh	Include an SPA fallback such as `/* /index.html 200` in `_redirects`
Backend feature fails	Remove the dependency or move it elsewhere; Linkyhost does not run servers, functions, or databases
Preview cannot use a domain	Deploy the ZIP again as Production; a seven-day preview is isolated and temporary

See Website Hosting for the production checklist and routing format.

A public link does not load

Expired: the chosen expiry has passed and deletion is scheduled. Publish a new link if the old one has been removed.
Free view cutoff: the account or serving owner reached the 250-view hard cutoff for the monthly period. Upgrade or wait for the monthly counter to reset.
Paid link inactive: a link created under a paid entitlement can stop serving after downgrade. Restore the workspace's paid plan.
Password prompt repeats: make sure cookies are allowed for the exact Linkyhost or custom domain, then enter the current password again.
Processing: wait briefly and reload.
Not found: check the entire URL and ask the owner whether the link was deleted or removed for policy reasons.

Password or PDF controls

Password protection supports PDF and HTML only and requires Pro.
A changed password replaces the old one immediately.
Password protection gates the hosted URL; it does not encrypt a downloaded PDF copy.
Prevent download & print is a PDF-only deterrent. Screenshots cannot be blocked.
Test protected links in a private window so an earlier unlock cookie does not hide the prompt.

Analytics problems

A successful visitor request must occur before a view appears.
Refresh after a short delay.
Direct traffic is expected when the sending app removes the referrer.
Country can be Unknown when the request lacks a location signal.
Unique visitors are approximate and can differ from real people.
Confirm the link and workspace are correct.

Read Analytics before treating the data as an identity or read-receipt system.

Custom domain problems

Status	What to check
Unverified	Add every TXT ownership value shown by the wizard and select Re-verify
Ownership verified, DNS broken	Correct the A or CNAME routing record; verification alone does not route traffic
Apex fails	Set `@`/blank A to `76.76.21.21` and remove conflicting apex records
Subdomain fails	CNAME its label to `cname.vercel-dns.com`
Cloudflare certificate problem	Change the record to DNS only instead of proxied
`www` fails	Remove a conflicting `www` record and point it to the Linkyhost/Vercel target shown in the domain status
Wildcard URL fails	Add the `*` CNAME and any requested certificate TXT records; wait for certificate issuance
Correct DNS but old site still appears	Wait for cached DNS to expire and verify at the authoritative DNS provider

Use the dashboard's live DNS diagnosis instead of relying only on your local browser cache. See Custom Domains.

Team and permission problems

The invitation must be accepted while signed in with the invited email.
Invitations expire after seven days; an admin can send a new one.
Revoke stale pending invitations when no seats appear available.
Members can edit only resources they created; admins and owners can edit any team resource.
A folder or domain must belong to the same workspace as the link.
The owner cannot leave; transfer ownership to an Enterprise member or dissolve the team.

API problems

Send Authorization: Bearer lh_..., including the Bearer prefix.
A full key is shown only once; generate another if it was not saved.
Revoked keys return 401.
Public API access requires the account to remain Enterprise.
A 429 response means the IP or owner request limit was reached; retry later with backoff.
The documented link list returns links authored by the key owner, including that person's own team-workspace links; it cannot list links authored by other team members.

See API Reference for the exact curl and response format.

Contact support

If the problem persists, contact support@linkyhost.com and include:

the exact error text;
the public link or custom domain, if safe to share;
the approximate time and timezone;
the file type and size, but not confidential file contents unless requested through an agreed channel;
whether this is Personal or a team workspace; and
the browser and operating system.

Never send a password, one-time sign-in code, complete API key, or billing-card details.

Still need a hand?