DEV Community: Bozhidar Valchev

Villagers Remember: Quests and Trust for Minecraft Villagers

Bozhidar Valchev — Wed, 21 Oct 2026 10:54:40 +0000

Villagers Remember is a mod for Minecraft 26.3, for Fabric and NeoForge, in which Minecraft villagers ask you for help and remember who helped them. It runs on the server, so players join with a normal vanilla client and install nothing. The first public beta, 0.13.0, is on CurseForge and GitHub. I publish it under my gaming name, SasnycoN.

Why I wanted it

In vanilla Minecraft a villager is a shop with a face. You trade with it and walk away. I have spent hours in trading halls and I couldn’t tell you the name of a single villager in them, because they don’t have one.

What I really wanted was something like Millénaire. I have been playing it since 2021, and my best friends in that world are the Byzantine traders of Istron, but Millénaire needs every player to install it. On our server my friends have one rule, the same one that gave me my other mod, Less Villager Chatter: nobody installs anything. So it had to use vanilla villagers and blocks and run entirely on the server.

Every villager is someone

Right-click a villager and they greet you based on what you’ve done for them. A stranger says “Hm. What do you want?” A villager you have helped for weeks says “You! The whole village talks about you.”

Each villager keeps their own memory of you, so Stoyan the farmer can be your best friend while the butcher next door has never heard of you. They all have names now, mostly old Bulgarian ones (in English Мария simply becomes Maria), and every village gets one of 230 names, many of them real Bulgarian villages.

Trust takes time. In a new village only one villager dares to talk to you, the one with the “!” (duh) over their head, and every time you help someone, one more opens up. Trading works too: keep trading with a villager until they reach a new level and they warm up to you. The ones you have traded with a lot already know you, which means the trading hall you have used for ages opens up at once.

To move up a tier with a villager, points aren’t enough. They give you a trial of trust first, a harder errand that pays double. Pass it, and they hand you the next set of errands.

Errands that pay fairly

Every villager with a job has a few errands a day. There are 21 kinds of tasks: craft, smelt, mine, harvest, fish, breed, kill, brew, enchant, find a structure and so on. The farmer wants twenty wheat, while the cartographer sends you to find a shipwreck.

I spent most of the balancing time on one question: is this worth doing? An errand always pays more than the same goods would bring from a villager, so it never makes sense to just trade instead. A first errand takes about five minutes for someone with no farms. A top one takes half an hour and can’t be pulled out of a chest, like an elder guardian or two zombie villagers to cure.

Errands pay experience and standing. Emerald rewards are off by default, because emeralds are the currency of trading and I didn’t want to flood the server with them. A server that wants them turns them on with one command.

Your standing also sets your prices, right in the normal trading screen: up to 40% off with a best friend in a village where you are the Hero, and up to 50% more if you hurt the village.

Something for the whole server

The biggest jobs aren’t for one player. Once a game month every village posts an order for everyone, sized by how many people play regularly: 512 food before winter for each of them, or 256 logs to fix the roofs after a storm. Anyone brings any amount, and when it’s done everyone is paid by their share.

For the long run there are weekly contracts, legendary items named after the villager who gave them (“Stoyan’s Hoe”), fame titles in chat and one patron per village. The patron is the player with the most standing there. Anyone who does more takes the place, and the whole server hears about it.

How it works with a vanilla client

This was the most fun part to build. The client knows nothing about the mod, so everything you see has to be something vanilla already knows how to show.

The menus are the dialog screens Minecraft added for servers, and each button in them just runs a command on the server. The “!” and “?” over villagers’ heads are text displays, the same entities map makers use for floating text, while the list of errands on the right is the old sidebar scoreboard. Even the language is decided on the server: the client reports which one it uses, and the mod answers in it.

One trap cost me some time. Villager names live in language files, and my first version kept them there as lists. Vanilla’s server-side language loader can’t handle lists in those files, so the names now live in files of their own.

The errands themselves are datapack JSON files, so a server can add its own.

Install

Take the file for your server’s loader:

Fabric: villagers-remember-0.13.0-beta.jar, with Fabric Loader 0.19 or newer and Fabric API
NeoForge: villagers-remember-neoforge-0.13.0-beta.jar, with NeoForge for 26.3

Drop it into the server’s mods folder. In singleplayer it works the same when installed on the client. Players with the mod on their client also get a settings screen, where server admins can change the server’s settings.

It’s a beta

It runs well on my test worlds, but a mod this size always has corners nobody has walked into yet. Balance is the part I’m least sure about, because five minutes of work for one player can be an hour for another.

The bigger plan comes after that. I’d like villages to grow the way they do in Millénaire, with villagers building new houses as the village prospers, and errands that send you to the next village over. That is still a long way off, but the mod already knows where each village ends and who lives in it, so it has somewhere to start.

If something breaks or feels off, come to the #villagers-remember channel on the ValcheffNet Discord. Write what happened in your own words and a person will answer. You don’t need a GitHub account for that.

Thanks

The villager heads in the screens come from Minecraft Heads, who kindly let me use them. Thank you.

The post Villagers Remember: Quests and Trust for Minecraft Villagers, Server-Side first appeared on Valcheff Net.

Scriptorium: Scraping Entire Documentation Sites and Document Archives to Markdown

Bozhidar Valchev — Thu, 08 Oct 2026 14:02:01 +0000

Scriptorium saves a documentation website to your own disk as Markdown, one file per page. It’s a command-line tool packaged as a skill for Claude Code and Codex. The actual converting is done by Microsoft’s MarkItDown. Scriptorium adds the parts MarkItDown doesn’t try to do: it finds the pages through the sitemap, puts each one in a folder tree shaped like the site, repairs the links between them and strips the menus and footers. Then it tells you what it did, and the numbers in that report have to balance. It also converts local documents, PDF, Word, PowerPoint and Excel, and a whole ZIP archive of them in one go. It’s free under the MIT license: github.com/valcheffnet/scriptorium.

I work with monitoring products, and their documentation runs to thousands of pages. I wanted it on my own disk for two reasons. I can search all of it at once instead of one browser tab at a time. And I can give it to an AI assistant, which then answers from the documentation instead of from memory. A model’s memory of a product is usually a few versions old and wrong on exactly the details you’re asking about.

The name comes from the room in a monastery where texts were copied by hand, one page at a time. That’s the whole design brief: an accurate copy of somebody else’s work, for your own reading.

GIF: GIF IT UP, CC BY-SA

Why I wrote it

It started as a workflow I put together to copy the Dynatrace documentation, about 4,400 pages. It did the job, but it was written for that one site and couldn’t be pointed at any other. It also lost content without telling me, and I found out piece by piece over several weeks.

What went wrong	What it cost
Filenames taken from the last part of the URL	534 of 4,389 pages silently overwrote each other
Icons deleted based on image width	1,453 table cells emptied on a single page
Heading ids dropped during conversion	46% of 8,992 links to a section pointed at nothing
Underscores in prose escaped by the converter	57,068 identifiers written as `CUSTOM\_DEVICE`, which a search for `CUSTOM_DEVICE` will never find
Inline `data:` images truncated	every such image on a page reduced to the same 24-character string

Every page converted and no error appeared. Each problem turned up by accident, long after I had trusted the output and built on it.

Embedded from Giphy. “This is fine” by KC Green.

The underscore one is my favorite, because it isn’t a bug in anyone’s code. MarkItDown uses a library called markdownify, and markdownify escapes _ and * in normal text by default, so they don’t turn into italics. In reference documentation most identifiers are written in plain text, without backticks. The page looks fine. The search returns nothing.

A converter that drops a table still reports success. That’s the problem Scriptorium is built around.

A report that has to add up

Every run prints a coverage equation, and it has to balance:

images = transcribed | skipped | queued | deleted
pages = converted | failed

Anything deleted is listed with its URL and the reason. This rule came from a bad afternoon. An earlier version counted an image nobody had looked at the same way as one that was deliberately skipped. In one afternoon I got three different progress numbers for the same work, 762, 596 and 561. The real number was 497.

So the tool keeps those two facts apart. “Nobody looked at this image” and “somebody looked and decided it was decoration” go in different columns.

How it works

Five stages. Only the fourth one needs a model.

Fetch and convert. It follows the sitemap and plans every output path before the first download, so a filename collision is caught in the plan and not discovered later as a missing page. Every file starts with the URL it came from.
Inspect the result. It looks for broken characters and compares the output size with the page size. Three kilobytes of text from a 700 KB page usually means the site renders in the browser and you got the menu.
Strip the site furniture. Navigation, cookie banners, breadcrumbs, footers and the little permalink icons next to headings.
Turn images into text. A diagram becomes an ASCII drawing plus a Mermaid diagram, a screenshot of code or a config becomes a code block or a table, and decoration is skipped with a written reason. This is the stage that costs model calls, so deciding which images are worth it matters more than the transcription.
Verify and report. It reads the files on disk instead of trusting what the earlier stages say they did.

The work from stage 4 is marked in the file with a comment that carries the image’s URL. If you fix a rule and convert the page again, the transcriptions you already paid for stay.

Install and first run

You need Python 3.11 or newer. It also works on 3.14.

git clone https://github.com/valcheffnet/scriptorium.git
cd scriptorium
python -m venv .venv
.venv/bin/pip install -r scripts/requirements.txt
.venv/bin/python -m scriptorium doctor

On Windows the pip line is .venv\Scripts\pip install -r scripts\requirements.txt.

Install through the requirements file, not with pip install markitdown[all]. On Python 3.14 that command finds nothing to install and stops. The worse case is plain pip install markitdown with no extras: it succeeds, and PDF and Office support is missing until the first time you need it. doctor checks for exactly that, along with the Python version and the User-Agent it will send.

The virtual environment takes about 420 MB. For what the tool does, that’s a lot, and most of it is MarkItDown’s dependencies.

To see the output before pointing it at anything big, convert a small public site. It takes about twenty seconds:

python -m scriptorium --profile mkdocs convert https://www.mkdocs.org/sitemap.xml -o ./try
python -m scriptorium verify ./try

Then open a few of the files. Always start with a pilot (--limit 3) and read what comes out. The rules for stripping menus are tuned from what you see there, and tuning them after a full run means converting everything twice.

One trap from Windows. Git Bash rewrites an argument that starts with a slash, like --strip-prefix /docs, into a Windows path before Python sees it. The run finishes with exit code zero and does none of the stripping. Scriptorium now refuses a prefix that looks like a Windows path, but the habit is the point. After a run, check what it actually did.

Use it as a skill

The repository is also a skill: SKILL.md sits at its root, in the open skill format that Claude Code and Codex both read. Clone it straight into the folder where your agent looks for skills, and the agent can run the whole procedure for you, including a folder full of documents.

For Claude Code, in your home folder, so it works in every project:

git clone https://github.com/valcheffnet/scriptorium.git ~/.claude/skills/scriptorium

For Codex the place is ~/.agents/skills/:

git clone https://github.com/valcheffnet/scriptorium.git ~/.agents/skills/scriptorium

Then set up the Python environment inside that folder, the same way as above. The skill tells the agent how to use the tool, and the tool does the work.

On somebody else’s server

The defaults assume the site isn’t yours. It reads and follows robots.txt, including Crawl-delay. It waits a second between requests to the same host and backs off when the server says it’s busy. The User-Agent says what the tool is. It only pretends to be a browser if you pass --as-browser, which is meant for your own sites.

It also shows you what the site says about AI use. A robots.txt with no ban can still declare that its content isn’t for AI training. A missing ban isn’t consent, so the tool reports that instead of stepping over it.

The output is a local copy of material somebody else wrote. Every file keeps its source URL. There’s nothing in the tool for putting someone else’s documentation back on the public web, and that’s on purpose.

What isn’t done yet

Scriptorium is that workflow rewritten to work on any site, with every one of those failures turned into a check or a test. The workflow behind it has copied the full Dynatrace documentation. The rewritten code itself has so far converted sites of up to 108 pages end to end. It comes with 32 offline tests that run in about a second, and five site profiles: generic, MkDocs, MkDocs Material, Docusaurus and Sphinx.

It doesn’t download images for you; it gives you the list of the ones worth transcribing. It doesn’t crawl sites without a sitemap yet, because calendars and search pages generate endless URLs, and a crawler without clear stop rules walks straight into them.

I’ve only run it on Windows 11. If you run the tests on macOS or Linux, I’d like to know the result, whether they pass or not.

What I learned

The code can be rewritten in a day. The list of ways HTML-to-Markdown conversion loses content took weeks of real failures to put together. It’s in references/traps.md, each one with how to spot it and what to do about it. If you already have a converted documentation set, read that file before you decide it’s fine.

My rule from all this: when a tool says it succeeded, open the file.

The post Scriptorium: Scraping Entire Documentation Sites and Document Archives to Markdown first appeared on Valcheff Net.

Manual WordPress Migration, Step by Step

Bozhidar Valchev — Thu, 01 Oct 2026 13:05:24 +0000

This WordPress migration guide moves a site from one host to another by hand. Files go over SFTP, the database through phpMyAdmin or WP-CLI, and DNS comes last. Every step has two versions. The first works with nothing more than a control panel and an SFTP client. The second is for readers who have SSH and want the job done in a few commands.

I first wrote this in 2015 on my old blog. Some advice from that version did not age well. One tip in it could even break a site without any warning, so this is a rewrite rather than a repost.

Numbers match the steps below.

When a manual WordPress migration makes sense

Migration plugins such as Duplicator, All-in-One WP Migration and Migrate Guru work well for most small sites. If one of them does the job for you, use it. Doing it by hand pays off when a site outgrows the plugin’s free tier or the new host’s upload limit. It also helps when a plugin migration has already failed and you need to see which step broke.

It also teaches you what a WordPress migration actually is. Every plugin does the same steps below, only out of sight.

Before you start

SFTP access to both hosts, and phpMyAdmin or SSH on both. Plain FTP sends your password in clear text, so use SFTP wherever the host offers it.
An SFTP client. FileZilla is fine; download it from the official site only. For SSH, Windows 10 and 11 already ship with OpenSSH, so ssh works from any terminal without PuTTY.
The site added as a domain or account on the new host. You also need an empty database, a database user and its password. If you are not sure how, ask the new host’s support.
The PHP version of the old site. In wp-admin it is under Tools > Site Health > Info > Server. Set the new host to the same version or a newer one that your theme and plugins support.
A lower DNS TTL. A day before the move, set the TTL of the domain’s A record to 300 seconds. The switch in step 9 then spreads within minutes instead of hours.

Plan a content freeze as well. Comments, orders and form entries that reach the old site after the export never make it to the new one. For a blog that means a quiet hour. For a WooCommerce shop it means maintenance mode.

1. Export the database from the old host

Without SSH, open phpMyAdmin and select the site’s database. Click Export, keep the Quick method and the SQL format, and click Go. If the database is large, choose the Custom method and set compression to gzip. phpMyAdmin imports .sql.gz files directly, and the compressed file is often a tenth of the size.

With SSH, go to the WordPress directory and let WP-CLI read the credentials from wp-config.php for you:

cd ~/public_html
wp db export ~/site.sql
gzip ~/site.sql

Keep this file even after the migration succeeds. It is your backup of the old site.

While you are in the database, note the table prefix. The tables are named something like wp_options and wp_posts, and the part before options is the prefix. You will need it in step 3.

2. Copy the files

Without SSH, connect to the old host with FileZilla and download the whole WordPress directory. First turn on Server > Force showing hidden files. Otherwise .htaccess stays behind, and with it your redirects and any custom rules. Then connect to the new host and upload everything into the site’s directory. Press F5 if new files do not appear in the listing.

Thousands of small files transfer slowly over SFTP. With a File Manager in cPanel or Plesk on both hosts, you can pack the directory into one archive. Move that single file and extract it on the new host.

With SSH, you can stream the files from one server to the other through your own computer. No archive lands on either disk, and the two servers never need access to each other:

ssh user@old-host "tar czf - -C ~/public_html ." | ssh user@new-host "tar xzf - -C ~/public_html"

Copy the full installation, core files included, rather than a fresh WordPress download plus wp-content. Both approaches work. The full copy has one less place for a version mismatch to hide.

3. Edit wp-config.php on the new host

Open wp-config.php in the new site’s directory and fill in the database you created on the new host:

define( 'DB_NAME', 'new_database_name' );
define( 'DB_USER', 'new_database_user' );
define( 'DB_PASSWORD', 'new_database_password' );
define( 'DB_HOST', 'localhost' );

Check DB_HOST with the new host instead of assuming localhost. Managed hosting and cloud databases often use a separate hostname. A wrong value gives you “Error establishing a database connection” and nothing else.

Further down the file, confirm that $table_prefix matches the prefix you noted in step 1. If it does not, WordPress finds no tables with that prefix and offers to install itself from scratch. Also look for absolute paths the old host needed, for example in WP_CONTENT_DIR or a cache plugin’s constant. Change them to the new server’s paths.

With SSH, WP-CLI edits the file for you:

wp config set DB_NAME new_database_name
wp config set DB_USER new_database_user
wp config set DB_PASSWORD 'new_database_password'
wp config set DB_HOST localhost

4. Import the database

Without SSH, open phpMyAdmin on the new host and select the empty database. Click Import, choose the file from step 1 and click Go. If phpMyAdmin rejects it as too large, compress it with gzip first. If it is still over the limit, ask the host’s support to import it for you. Most will do it within the hour.

With SSH, upload the file and import it from the WordPress directory. WP-CLI takes the credentials from the wp-config.php you just edited, which is why step 3 comes first:

cd ~/public_html
gunzip ~/site.sql.gz
wp db import ~/site.sql

One error comes up often when the old host runs MySQL 8 and the new one runs MariaDB: Unknown collation: 'utf8mb4_0900_ai_ci'. MariaDB does not know that collation. Open the .sql file in a text editor, replace every utf8mb4_0900_ai_ci with utf8mb4_unicode_ci, and import again. This replacement is safe, because it touches table definitions and not your content.

5. Replace the old domain and paths

Skip this step if the domain stays the same and nothing in the database points to the old server’s directories. Otherwise, this is the step where most manual WordPress migrations go wrong.

The 2015 version of this guide told you to open the SQL file in Notepad++ and replace the domain there. Do not do that. WordPress and its plugins store widgets, theme options and plugin settings as serialized PHP. In that format the length of every string is written next to it, for example s:22:"http://old-domain.com/". Change the domain to one of a different length and the stored length no longer matches. WordPress cannot read the value and silently drops it, so widgets, menus and theme settings disappear with no error message.

With SSH, WP-CLI understands serialized data. Run it with --dry-run first, which only reports how many replacements it would make:

wp search-replace 'https://old-domain.com' 'https://new-domain.com' --all-tables --skip-columns=guid --dry-run
wp search-replace 'https://old-domain.com' 'https://new-domain.com' --all-tables --skip-columns=guid

The same command fixes old server paths, such as /home2/olduser/public_html replaced with the new site’s directory. Some plugins store those for caches, logs and uploads. After a move they point to a directory that no longer exists.

Without SSH, use Search-Replace-DB by interconnect/it. Upload its folder to the site’s root under a random name that nobody will guess. Open it in the browser, run a dry run, then the real replacement. Delete the folder right after. Left on the server, it gives anyone who finds it full write access to your database.

6. Test the new site before DNS changes

The domain still points to the old host, but your own computer can be told otherwise. Add a line to your hosts file with the new server’s IP address:

203.0.113.10 example.com www.example.com

On Windows the file is C:\Windows\System32\drivers\etc\hosts and needs an editor started as administrator. On macOS and Linux it is /etc/hosts. Restart the browser and click through the site: the home page, a few posts, the contact form and the wp-admin login. The new host probably has no SSL certificate for the domain yet, so expect a certificate warning at this stage. Everything else should work.

Remove the line when you are done. Otherwise you will never notice if DNS itself is wrong, because your computer keeps going straight to the new server.

7. Fix file permissions

Files copied from another server sometimes arrive with the wrong permissions. WordPress expects 755 for directories and 644 for files. With SSH, run this in the WordPress directory:

find . -type d -exec chmod 755 {} +
find . -type f -exec chmod 644 {} +
chmod 640 wp-config.php

The + at the end passes many files to one chmod call. That is much faster than one call per file. wp-config.php holds the database password, so it gets tighter permissions. If the site shows a white page after the last command, PHP runs under a different group on that host. Try 600, or ask support which value they recommend.

Without SSH, FileZilla can do the same. Right click the WordPress directory, choose File permissions, enter 755, tick Recurse into subdirectories and select Apply to directories only. Repeat with 644 and Apply to files only.

8. Flush permalinks and caches

In wp-admin, open Settings > Permalinks and click Save Changes without changing anything. This rebuilds the rewrite rules and fixes most “404 on every page except the home page” problems after a move. Then clear the cache of any caching plugin and of the CDN, if you use one.

wp rewrite flush
wp cache flush

9. Switch DNS

At your DNS provider, point the A record of the domain and of www to the new server’s IP. Do the same for the AAAA record if you have one. Leave the MX records alone unless your email is moving as well. It is easy to break email with a migration that was only meant to move a website.

With the TTL lowered a day earlier, most visitors reach the new server within minutes. Some resolvers ignore TTL, so keep the old hosting account running for at least a week.

10. Issue the SSL certificate

Let’s Encrypt checks that the domain points to the server asking for the certificate. This step therefore waits until DNS has switched. Most control panels issue it with one click, often automatically. If the site then shows a padlock with a warning, some content still loads over http://. Run the search-replace from step 5 again, from http://example.com to https://example.com.

If the browser shows “Your connection is not private” after the switch, my guide on fixing that SSL error walks through the usual causes.

11. Check the error log

Every host is configured a little differently. A plugin that ran quietly on the old server may complain on the new one. The host’s PHP error log is usually in the control panel. For WordPress’s own log, add these lines to wp-config.php for a day or two:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Errors then go to wp-content/debug.log without showing on the page. Set WP_DEBUG back to false when you are done. On many servers the log file is readable from the web. If you cannot make sense of an error, send it to the new host’s support. That is part of what you pay them for.

After the move

Keep the old hosting and the database dump for at least a week. Watch the error log and check that contact forms still send email. Also open the site from a phone on mobile data, which uses a different DNS resolver than your home network. Cancel the old account only when a week has passed without surprises.

What about letting an AI agent do it?

I tried. For this rewrite I wrote a prompt for a coding agent with shell access. I ran it with Claude Code against two throwaway WordPress servers in Docker. The agent did the first half well. It took an inventory of both hosts and noticed the non-default table prefix. After a backup of the database and the files, it streamed the files across. It filled in wp-config.php without ever printing a password, and it stopped for approval where the prompt told it to.

Then it reached the database import. Claude Code’s own safety layer refused to run it, even after I had approved the step. Overwriting a database on a remote server is exactly what these tools leave to a person. I think that is the right call. It does mean the riskiest step of the whole migration stays with you. An agent can save you time on the preparation and on checking the result afterwards. Plan to run steps 4 and 5 yourself.

If this still feels like too much, hiring someone to do it is a perfectly reasonable choice. A broken migration usually costs more than a paid one.

The post Manual WordPress Migration, Step by Step first appeared on Valcheff Net.

In Search of the Best A.I. Literary Translator – Detailed

Bozhidar Valchev — Tue, 29 Sep 2026 20:08:52 +0000

My wife reads faster than books get translated into Bulgarian. Some of the ones she wants don’t exist in Bulgarian and probably never will, because the market is small and the translation doesn’t pay for itself.

So I tried machine translation. It came out unreadable: sentences that are grammatically correct and mean nothing, and dialogue punctuated the English way. My wife got to page thirty and gave up.

I started with DeepL, which everyone calls the best. It turned out to be all talk, and later in the test it came last of ten.

The same happened with qwen3.8-max. I only included it because it is supposedly the best model for translation. It came second to last and was the only one that dropped parts of the text. All talk again.

So I decided to run my own study and find out which AI literary translator really does the job best. In Bulgarian specifically, because a model that translates beautifully into Spanish isn’t necessarily good at Bulgarian, and the English-language rankings say nothing about it. Bulgarian has things English doesn’t. Gender follows the word the translator chose, so the same ship is correctly “she” if you called it a galley and “he” if you later called it a ship. The definite article sticks to the end of the word, there is a separate mood for retelling what you didn’t witness, and dialogue opens with a dash. At every one of those points the models differed.

What I wanted to find out

Which model, with what processing around it, can translate a work of fiction into Bulgarian well enough that someone finishes the book. I also wanted to know whether it is possible to measure at all who translates better.

How I tested the AI translators

I took Robert E. Howard’s story “Shadows in the Moonlight” from 1934. Howard died in 1936, so in the EU the text has been free since 2007. The story is 296 paragraphs and 12,079 words. As a yardstick I used an old published human translation: 305 paragraphs and 12,276 words, with every paragraph of the original matched to one in it.

The translators were eight language models: gpt-6-astra, claude-opus-5, gemini-3.1-pro, gemini-3.8-flash, deepseek-v4-pro, grok-4.6, kimi-k3 and qwen3.8-max. Next to them I put DeepL, which is not a language model and serves as the floor. All of them ran through the same translation setup, and every model got byte for byte the same task. In the first round they all translated with no extra steps.

I scored them three ways. First, mechanical checks over the whole text. Then a full read of all 296 paragraphs of every translation against the original, by the same reader, Fable 5.1, with serious, moderate and minor errors defined in advance. And finally a blind comparison: six passages from the ten translations, unlabelled and shuffled, in front of four judges from four different makers, Fable 5.1, Astra Pro, Gemini Pro and DeepSeek. Each of them has a relative among the translators, which is why there were four.

There were a few rules. The judges don’t know who translated what. They score all the translations at once, so they measure on the same scale. Their instructions also explain how gender works in Bulgarian, because without that almost every translation looked wrong. And I checked whether the models had seen the published translation during training.

What came out

Whether a model works depends on who answers the call

Most models are bought through a middleman, and behind one model name a different company can answer each call. For DeepSeek the catalogue lists 16 such companies, for Kimi 20. Behaviour changes with whichever company answers.

Through one of the providers, deepseek-v4-pro cut the translation off at every ceiling I tried: 6,000, 16,000 and 48,000 tokens. Directly through DeepSeek’s own API it translated the whole story without a single break. gemini-3.8-flash through Google AI Studio returned 19 empty responses and stopped at 20% of the book, while through Google Vertex it went all the way. My first thought was censorship, because blood gets spilled in the story. I repeated the same call nine times and the empty response never came back. It was a temporary fault at the provider.

One of the failures was mine: out of habit I set a ceiling of 32,000 tokens on DeepSeek, and the translation stopped exactly there. Since then I pin the provider explicitly and check it with a live call before I start the big book.

Counting can’t tell a good translation from a bad one

The mechanical checks count words, dialogue lines, dashes, quotation marks, very short paragraphs, and missing or repeated paragraphs. One solid thing came out of it: none of the nine dropped a whole paragraph. After that, counting stops helping.

Six of the models come out practically identical: length between 0.948 and 0.975 of the original and 150 or 151 dialogue lines with a dash. kimi-k3 has excellent numbers and a text full of words that don’t exist in Bulgarian, and in the blind comparison it is among the last. Reading split those same six models into four clearly different levels. Counting only catches the obvious failures.

The full read produced these findings:

Translation	Findings, count	Severe, count	Moderate, count	Minor, count
gemini-3.1-pro	15	0	4	10
gpt-6-astra	22	0	6	15
grok-4.6	92	0	24	68
gemini-3.8-flash	57	1	14	42
deepseek-v4-pro	77	1	30	45
human translation	125	2	13	105
claude-opus-5	89	4	30	55
kimi-k3	70	8	53	9
qwen3.8-max	108	15	25	68
DeepL	146	16	79	46

The totals aren’t quite comparable, because each reader decides for itself what to note. The serious column is comparable, because serious was defined the same way for everyone. DeepL is last with 16, and almost all of them are words with two meanings. “Quarter!”, which in a fight is a plea for mercy, becomes “Четвърт!”, the fraction. “Painter”, the rope on a boat, becomes “Художникът”, the artist. In one paragraph the word is wrong, in the next it is right, because every sentence is translated on its own. qwen3.8-max drops text and the reader feels the gap. DeepL writes smooth Bulgarian that says something else, and an editor without the original in front of them won’t catch it. According to the reader, bringing the DeepL translation up to print costs 60 to 70% of a new translation.

Which AI literary translator came out best in the first round

One judge gave only an order without points, so the chart shows three. The first three places are the same for every judge: gpt-6-astra, gemini-3.8-flash and deepseek-v4-pro. Further down, opinions differ by up to three places.

I also checked how much each judge goes easy on its relative. Fable 5.1 doesn’t move claude-opus-5 at all, Astra Pro lifts gpt-6-astra by 0.33 places, DeepSeek lifts its own model by one place, and Gemini Pro lifts gemini-3.8-flash by 1.33 places and gives it 10 out of 10 on all six criteria, the only perfect score in the first round. The bias is real but small: if I remove each judge from the scoring of its own family, the top doesn’t move.

Slower doesn’t mean better

gemini-3.8-flash is the fastest, seven and a half minutes for the whole story, and it is second in the ranking. grok-4.6 works 10.5 times longer and comes in sixth or seventh. Waiting longer doesn’t buy a better translation.

What a translation pipeline adds

A plain translation is one pass through the text. A translation pipeline adds extra processing around that pass. I tried one on the four best models from the first round. The other four stopped here, because the same effort on a model four levels down answers nothing new.

Each model’s plain translation and its pipeline versions were scored side by side by one blind judge, so compare the points only within one model. gpt-6-astra goes up from 6 to 8 points, gemini-3.1-pro from 7 to 8. gemini-3.8-flash drops from 8 to 7, deepseek-v4-pro from 7 to 6. For both drops the judges say the same thing: the translation becomes more precise in detail and in gender, but pays for it with literalisms and words that don’t exist. So there is no general answer to whether you should switch a pipeline on. It depends on the model, and the only way to find out is to try both.

If you just add up the findings, the pipeline looks harmful: 90 before, 106 after. The breakdown shows the opposite. Moderate errors fall from 29 to 19, while minor remarks rise from 60 to 87, and that holds for each of the four models on its own. The pipeline trades errors of meaning for style remarks. Four out of four in the same direction happens by chance once in sixteen times, so it is a signal, but not yet proof.

The human translation came in below the best machines

Across the different scorings the published translation sits between sixth and eighth place out of ten. Its biggest loss is completeness, 4 out of 10, the lowest score after qwen3.8-max, which really does drop text. The translator condenses on purpose. Of 125 departures from the original, 66 are deliberate choices, 35 are errors of meaning and 23 are language or typography. The criterion, though, counts every cut as a loss, even when it works. The human translation has both errors and style, and this scale only sees the errors.

Completeness isn’t the only reason. For Bulgarian the translation gets 6 out of 10, level with claude-opus-5 and below four of the machines: gpt-6-astra gets 9, gemini-3.8-flash gets 8. It keeps using the short definite article where Bulgarian grammar needs the full one. There is wrong verb government too, one case of it twice. About ten technical errors remain in the text, such as a line-break hyphen in the middle of a word, doubled words and Latin letters inside Cyrillic words. On gender it scores 8 out of 10, and the review finds one such slip: once Olivia turns masculine. These most likely come from scanning the text, not from the translation. The articles and the verb government, though, are in the translation itself.

The translation is by Ivan Zlatarski, made around 1991 for a publisher, with no editing or proofreading, as was common at the time. Where and how it appeared in print is still unclear. It is probably in the 2003 Bulgarian collection “Конан: Пътят на славата” (Elf), which credits a different translator. That explains both kinds of errors: the articles come from a fast translation, and the technical errors from scanning the book.

The models hadn’t seen the translation before

The published translation may have ended up in the data the models were trained on. Then they would simply be remembering it. I checked two ways. First, the longest common run of words: between a model and the human translation it averages 5.2 to 5.7 words, and between the models themselves 8.8. Then I gave the models a passage of the human translation and asked them to continue: the continuation resembles the human as much as it resembles their own translation. Nothing stands out. The stronger check, the same test on a book with no published Bulgarian translation, I skipped on purpose.

The second round: the judge sits down to translate

After the first round, Fable 5.1 did all the reading and scoring. For two days it checked other people’s translations without handing in one of its own. So I had it translate the story too, with the same instructions as the other models. Like the four best models, it made a plain translation and versions through the pipeline, three texts in all.

Fable couldn’t judge its own translation, so two outside judges scored it, gemini-3.8-flash and deepseek-v4-pro. And all the translations came back into play. The ten from the first round plus Fable’s three, thirteen texts at once in front of each judge, on the same six passages. It doesn’t work any other way: an eight given without knowing there is a nine in the same room isn’t the same eight.

gpt-6-astra stays first. Fable is right behind it. But I don’t count it as a win, because the conditions favoured it. It knew what it would be judged on: its rules were written after the first round and answer exactly the errors the others were penalised for. And once it caught and fixed its own error by itself, a Latin “p” inside a Bulgarian word. This round shows what a well-tuned process adds. Which model translates better is a different question.

One of Fable’s pipeline versions came out byte for byte the same as its plain translation, because the extra processing changed nothing. That is how two identical texts ended up in the blind comparison without anyone planning it.

What I learned about measuring itself

The same reader doesn’t repeat its findings

Some pipeline versions differ from the plain translations by only a few paragraphs, and the same reader read both. In practice that is the same text read twice.

Only 68% of the paragraphs with a remark on the first read have a remark on the second. On average 14 findings per text appear or vanish in paragraphs the pipeline never touched. So on 296 paragraphs the finding count has an error of about 10 to 15. The difference between 15 and 22 findings doesn’t exist. The difference between 15 and 92 does.

The second round gave a cleaner experiment. Fable’s two identical texts went into the blind comparison under different letters. The judges saw them as two different candidates and gave them identical scores on all six criteria. So the disagreement comes from splitting the reading into several sittings, and when a judge sees everything at once, it is precise. Hence the rule: score everything in one call.

How I almost published an error that doesn’t exist

The first scoring instruction checked gender the way an English speaker would. In English the ship and the galley are both “it”, so a translation that says “ще го огледаме” (masculine) about the ship and “ще я потопя” (feminine) about the galley looked confused. By that rule almost every translation had a gender error, and for a while I had it written down as a finding. There is no such error. “Галера” is feminine, “кораб” is masculine, so both are right. Seven of the ten readers noticed it on their own, and that is how I noticed it too. After I rewrote the rule, “almost all” shrank to one real gender error in the blind comparison. The instruction has to carry the rules of the language even when most readers know them, because the rest will fill the table with errors that aren’t there.

What this study doesn’t prove

Everything rests on one story of 12,079 words. The next step is a longer book with the top three models.
Most numbers after the first round come from a single reader, and that reader repeats only 68% of itself.
The pipeline result is four out of four in the same direction. It is a signal until a second book says otherwise.
Thirteen candidates on a ten-point scale squash the top. At one judge three of them share the ten.
The stronger check of whether the models know the human translation, with a book that has no published translation, hasn’t been done yet.

So which model translates fiction best

Overall, gpt-6-astra showed the best results in every round.

gemini-3.8-flash came second, and it is by far the fastest of the eight.

I also saw that a translation pipeline can change the result noticeably, in either direction depending on the model. If I set out to translate fiction myself, I would do it with a pipeline, tuned to the model I pick.

The short version of this article is here: In Search of the Best A.I. Literary Translator.

Originally published at valcheff.net.

In Search of the Best A.I. Literary Translator

Bozhidar Valchev — Tue, 29 Sep 2026 20:08:40 +0000

So I tried machine translation. It came out unreadable: sentences that are grammatically correct and mean nothing, and dialogue punctuated the English way. My wife got to page thirty and gave up.

I started with DeepL, which everyone calls the best. It turned out to be all talk, and later in the test it came last of ten.

How I tested the AI translators

So I decided to run my own study and find out which AI literary translator really does the job best. I took a Robert E. Howard story of about 12,000 words that also has a published human translation, and gave it to eight language models and to DeepL. Every one of them got the same instructions, word for word.

For the scoring I picked four models from four different makers. Each has a relative among the translators and may go a little easy on it, so with four the bias gets diluted, and I can also see whether their scores agree. I set a few rules as well. The judges don’t know who translated what, and they score all the translations at once, so they measure on the same scale. I also checked whether the models had seen the published translation during training, because then they would simply be remembering it. I found no sign of that.

Which AI literary translator came out on top

Here is how they ranked. One judge gave only an order without points, so the chart shows three.

What the pipeline adds

Based on these results I also tried a translation pipeline, which adds extra processing around the plain translation.

I ran the four best models again, this time through the pipeline. gpt-6-astra and gemini-3.1-pro gain one or two points, while gemini-3.8-flash and deepseek-v4-pro lose one. Each model was scored only against its own versions, so compare it only with itself.

The human translation, and the judge as a translator

I also scored the published human translation. It came in below the best machines, and the main reason is completeness. The translator cuts on purpose: of 125 departures from the original, 66 are deliberate choices, and the scoring counts every one of them as a loss, even when the cut works. It also loses points on language. It keeps using the short definite article where Bulgarian grammar needs the full one: “кимериеца”, “вашия капитан”, “пътя ти”. There is wrong verb government too, such as “пусни ни борда”, and that one appears twice. About ten technical errors remain in the text, such as a line-break hyphen in the middle of a word (“удивле-ние”), doubled words and Latin letters inside Cyrillic words. These most likely come from scanning the text, not from the translation. For Bulgarian it scores 6 out of 10, against 9 for the best model.

The translation is by Ivan Zlatarski, made around 1991 for a publisher, with no editing or proofreading. Where it appeared in print is still unclear.

Finally I had one of the judges, Fable 5.1, translate the story too, plain and through the pipeline. Two outside models scored it together with all the other translations at once, so the scale was shared. It came right after gpt-6-astra, but I don’t count that as a win, because it was the only one that knew in advance what it would be judged on.

So which model translates fiction best

Overall, gpt-6-astra showed the best results in every round.

gemini-3.8-flash came second, and it is by far the fastest of the eight.

Here you can read the detailed article about the research: In Search of the Best A.I. Literary Translator – Detailed.

Originally published at valcheff.net.

Download YouTube playlist and channel videos with yt-dlp

Bozhidar Valchev — Sun, 13 Sep 2026 22:41:05 +0000

YT playlist downloader is a single Python script that uses yt-dlp to download YouTube playlist videos in bulk. It handles entire channels and single videos too. It numbers the files in playlist order and remembers what it has fetched, so an interrupted run resumes where it stopped. A private or deleted video does not stop it either. The source is on GitHub under the MIT licence: YT_playlist_downloader_by_Valcheff.

Use it for material you have the right to download. That covers your own uploads, Creative Commons and public domain video, or anything the uploader permits. DRM protected streams are out of scope, and yt-dlp cannot handle them at all.

What it does

yt-dlp can already do everything below. The catch is that doing it well takes a very long command line. Most people rebuild it from the help output every time and quietly leave out the parts they forget. The script fixes the flags in place so a bulk download behaves sensibly by default.

Files keep the playlist order, the archive makes re-runs resume, and an unavailable video is skipped.

Files land in playlist order

Each filename starts with its position in the playlist. A 40 part lecture series therefore stays in sequence on disk instead of sorting alphabetically by title. It also sanitises titles for Windows and caps them at 200 characters, so long names stay under the path limit.

Interrupted downloads resume

The script writes every completed video ID to an archive file in the output directory. Stop a 300 item playlist at item 180 and run the same command a week later. It continues at 181 rather than starting over. Partially written files resume at the byte level too, so a video cut off midway is not downloaded twice.

One dead video does not stop the run

The script logs and skips private, deleted and geo-blocked items, and the rest of the playlist still downloads. Without this, a single unavailable video at position 47 ends a 200 item run. That is the main reason unattended downloads fail overnight.

Requirements

Python 3.9 or newer
yt-dlp installed with its default dependency group
ffmpeg on PATH, for merging video with audio and for audio conversion
deno 2.3.0 or newer, which yt-dlp uses to solve YouTube’s JavaScript challenge

pip install -U "yt-dlp[default]"

The quotes and the bracketed group matter. A plain pip install -U yt-dlp omits the challenge solver, which produces a misleading failure covered in the troubleshooting section.

How to download YouTube playlist videos

Start by listing the playlist. This prints the contents with numbers and durations and downloads nothing. It matters because a channel URL with 1100 videos looks identical to a playlist with 12 until you check.

python yt_playlist_dl.py "https://www.youtube.com/playlist?list=PLxxxx" --list

Then take the first two items as a smoke test. It catches a wrong output path or a missing ffmpeg before a long run does:

python yt_playlist_dl.py "URL" -o "D:/Video" --items 1-2

If those arrive correctly, drop the item range and download the whole playlist:

python yt_playlist_dl.py "https://www.youtube.com/playlist?list=PLxxxx" -o "D:/Video"

Files arrive as D:/Video/<playlist name>/01 - Title [videoID].mp4 and so on. Pass --flat if you would rather skip the per-playlist subfolder.

How to download an entire YouTube channel

Point it at the channel’s videos tab. Channels list newest first. Add --reverse to make the oldest video file number one, which suits a course or a series:

python yt_playlist_dl.py "https://www.youtube.com/@channel/videos" -o "D:/Channel" --reverse

Large channels are worth splitting into batches with --items, for example 1-100 today and 101: tomorrow. The archive file makes the split safe, because the second run skips anything the first one finished.

To keep a channel mirrored, save the URLs in a text file and re-run the same command whenever you like. It downloads only the new uploads:

python yt_playlist_dl.py -f channels.txt -o "D:/Video"

How to download audio only

To download YouTube playlist audio without the video, add --audio-only. For podcasts, lectures and music this cuts roughly ninety percent of the transfer. The script never touches the video stream:

python yt_playlist_dl.py "URL" -o "D:/Podcasts" --audio-only --audio-format opus --thumbnail

Choose opus rather than mp3 where your player allows it. YouTube already serves audio as opus or m4a. Requesting mp3 makes ffmpeg re-encode an already lossy stream, which adds a second round of loss. With opus you keep the original bytes. mp3 is worth it only for hardware that cannot play anything else. flac is counterproductive: it multiplies the file size without recovering detail YouTube has already discarded. The --thumbnail flag embeds the video thumbnail as cover art, which is what most music players display.

How to download videos with subtitles

python yt_playlist_dl.py "URL" -o "D:/Course" --subs --auto-subs --sub-langs en,bg --embed-subs

Without --auto-subs you get only captions the uploader typed by hand, which for most amateur video means none at all. Adding it brings in YouTube’s machine transcript, which is useful for searching through lectures even though it reads poorly. --embed-subs writes the subtitles inside the video file instead of leaving separate .srt files next to it. That matters for players that fail to pick up external subtitle files.

Choosing quality and file size

The default ceiling is 1080p. It controls size more than quality, because 4K files are five to eight times larger than 1080p ones. The selector always takes the best format below the ceiling. A 480p source stays 480p, and the script never upscales it.

python yt_playlist_dl.py "URL" -o "D:/Video" --max-height 2160 # up to 4K
python yt_playlist_dl.py "URL" -o "D:/Video" --max-height 720 # small files
python yt_playlist_dl.py "URL" -o "D:/Video" --max-height 0 # no limit

Output goes into an mp4 container by default, which plays on essentially everything and spares media servers from transcoding. Switch to --container mkv when you are pulling several subtitle languages or want chapters preserved, since mp4 handles both badly.

Resuming and re-running

The script records completed video IDs in .downloaded.txt inside the output directory, and every later run skips them. Interrupt with Ctrl+C at any point and run the identical command afterwards to continue.

Two consequences are worth knowing. Moving the finished files elsewhere does not clear the archive, so the script will not fetch them again. To download the same playlist again at a different quality, point -o at a new directory or pass --no-archive.

For an overnight run on a shared connection, cap the speed and slow the request rate:

python yt_playlist_dl.py "URL" -o "D:/Video" --rate-limit 3M --sleep 1 --fragments 3

Fragments deserve a word, because they are the main speed lever. A large video arrives in hundreds of fragments and the script downloads four at a time by default. Beyond roughly eight, YouTube throttles and intermittently returns HTTP 403. The retries that follow end up slower than a lower number would have been.

All options

Option	Effect
`--list`	Print the playlist contents and download nothing
`-o DIR`	Output directory
`--flat`	Skip the per-playlist subfolder
`--items SPEC`	Select items: `5-20`, `3,7,12`, `5:`, `::2`
`--reverse`	Walk the playlist from the end, for channels that list newest first
`--max-height PX`	Resolution ceiling, 1080 by default, `0` for unlimited
`--container`	mp4, mkv or webm for the merged file
`--audio-only`	Download the audio stream only
`--audio-format`	opus, m4a, mp3, flac, wav or vorbis
`--subs`, `--auto-subs`	Subtitles, optionally including machine generated ones
`--embed-subs`	Write subtitles inside the video file
`--thumbnail`	Embed the thumbnail as cover art
`--sponsorblock`	Cut sponsor segments using the SponsorBlock database
`--fragments N`	Parallel fragment downloads per video, 4 by default
`--rate-limit RATE`	Speed ceiling such as `3M` or `800K`
`--sleep SECONDS`	Pause between requests
`--cookies-from-browser`	Use an existing browser session for your own private videos
`--no-archive`	Ignore the resume archive and download everything again

Troubleshooting

Every download fails with “This video is not available”

The message is wrong and the video is fine. YouTube hides its stream URLs behind a JavaScript challenge. yt-dlp solves it by running an external JavaScript runtime, deno by default, over solver scripts from the separate yt-dlp-ejs package. When the solver is missing, no formats come back and yt-dlp reports the absence of formats as an unavailable video.

Installing with the dependency group shown earlier pulls the solver in and fixes it. Official GitHub release binaries bundle it already, so this only bites pip installs. Verify both halves like this:

python -c "import yt_dlp_ejs; print('solver present')"
python -m yt_dlp -v --simulate "https://www.youtube.com/watch?v=SOME_ID"

The verbose output should report JS runtimes: deno-<version> followed by Solving JS challenges using deno. If it reports no supported runtime while deno is definitely installed, your terminal predates the installation. Its PATH is stale, so open a new one. Keep the two packages in step. yt-dlp raises the minimum solver version without announcing it and silently ignores an outdated one.

Downloads are slow or return HTTP 403

Lower --fragments to 2 or 3 and add --sleep 1. If it persists across a whole session rather than one video, YouTube is rate limiting your address. Waiting is the only real fix.

Merging fails or audio only produces nothing

ffmpeg is not on PATH. Run ffmpeg -version to confirm, and reopen the terminal if you installed it in this session.

Frequently asked questions

Can it download an entire YouTube channel?

Yes. Pass a channel videos URL such as https://www.youtube.com/@channel/videos and it walks every upload. Channels list newest first, so add –reverse for chronological order.

Can it resume an interrupted playlist download?

Yes. The script records completed video IDs in an archive file inside the output directory. Re-running the identical command skips them. Half finished files also resume at the byte level.

How many videos can it download at once?

There is no built in limit, and playlists of several hundred items are the normal case. It fetches videos one after another while the fragments inside each video download in parallel. That keeps the request rate low enough to avoid throttling.

Do I need YouTube Premium?

No. yt-dlp downloads the same streams an anonymous viewer receives. It never fetches ads, because YouTube delivers them separately from the video stream. A Premium account changes one thing: it makes the enhanced bitrate 1080p format available. yt-dlp labels that format Premium and prefers it automatically when you pass –cookies-from-browser. Everything else works identically without a subscription.

Can it download private or age restricted videos?

It can use your own browser session through –cookies-from-browser. That covers your own unlisted and private uploads and age gated material. It does not bypass any restriction; it only reuses the access you already have.

Which audio format should I choose?

opus, because YouTube already serves opus and nothing needs re-encoding. Choose mp3 only for players that cannot handle anything else.

Source

One script, one README documenting every option with the reasoning behind it, MIT licence: github.com/valcheffnet/YT_playlist_downloader_by_Valcheff. It calls yt-dlp as a Python library rather than shelling out. Progress reporting, error handling and the resume archive all run through the API.

valcheffnet / YT_playlist_downloader_by_Valcheff

Download YouTube playlists and channels with yt-dlp: playlist-ordered filenames, resume across runs, and per-item error tolerance

YT playlist downloader

A yt-dlp wrapper for pulling down whole YouTube playlists and channels without having to remember twenty command line flags every time.

It handles the parts you would otherwise write yourself. Filenames keep the playlist order. Anything already downloaded gets skipped on the next run. And when one item in a 200 video playlist turns out to be private, the other 199 still arrive.

Meant for material you have the right to download. Your own uploads, Creative Commons and public domain video, amateur footage, anything the uploader allows It does not touch DRM protected streams and cannot be made to.

Prerequisites

What	Why	Check
Python 3.9 or newer	runs the script	`python --version`
yt-dlp with the `default` dependency group	does the actual work	`python -m yt_dlp --version`
ffmpeg on PATH	merges video and audio, converts audio, embeds subtitles	`ffmpeg -version`
deno 2.3.0 or newer	solves YouTube's JavaScript challenge

…

View on GitHub

The post Download YouTube playlist and channel videos with yt-dlp first appeared on Valcheff Net.

Fix SSL “Your connection is not private”

Bozhidar Valchev — Wed, 12 Nov 2025 17:52:39 +0000

When Chrome or Firefox shows “Your connection is not private” or “Your connection is not secure” on your domain, your visitors cannot trust your site. In most cases this means there is a problem with the HTTPS / SSL configuration of your own website.

This guide is for website owners. It shows you how to check and fix this error on your site by testing the SSL certificate, the domain configuration, and the certificate chain.

What this error means for your website

Modern browsers show this warning when they detect that:

the SSL certificate does not match the domain, or
the certificate has expired, or
the server does not provide a full, trusted certificate chain, or
the site redirects to a host without a valid certificate.

From a visitor’s perspective, the message says:

“Do not enter passwords or credit card details here. Someone might read your traffic.”

As a site owner, you should treat this as a configuration bug on your side and fix it as soon as possible.

Step 1: Check your SSL certificate with an online tool

First, verify that your SSL certificate is installed and working correctly.

There are many free online tools that can test this. One simple and reliable option is:

https://www.sslshopper.com/ssl-checker.html

Step 2: Make sure the domain matches the certificate

A very common cause of the “your connection is not private” error is a mismatch between the domain name and the SSL certificate.

In the SSL report, check that:

your exact domain appears in the certificate,
any subdomains you use over HTTPS are also covered,
you understand the difference between domain.com and www.domain.com.

If the certificate only covers www.domain.com and your site loads from domain.com (without www), users may see a warning. The same happens in the opposite case.

If you see a mismatch:

update the certificate so it includes all domains you actually use, or
adjust your redirects so visitors always land on the hostname that the certificate covers.

Step 3: Check where your site actually loads from

Next, make sure your domain points to the correct server and host.

Look at:

the A/AAAA records in your DNS,
any redirects your site performs,
the final hostname in the browser address bar.

Typical problems:

your DNS points to an old server without a valid certificate;
your site redirects from https://yourdomain.com to another host like https://some-default-host.yourprovider.com that uses a different certificate.

In these cases the browser sees a certificate for another domain and shows the warning.

Step 4: Review all checks in the SSL report

In the SSL checker result you will see several checks. Go through them one by one and confirm they all pass.

Pay attention to:

Validity: has the certificate expired?
Hostname: does the certificate match your domain?
Trust: is the certificate issued by a trusted Certificate Authority?
Chain issues: is the server sending the full certificate chain?

If something is wrong, the tool will usually show a red or orange warning, together with a short explanation.

Step 5: Install the full CA chain

Your server should not only send your main SSL certificate but also the intermediate CA certificates that link it to a root CA trusted by browsers. Together, this is known as the certificate chain.

If the chain is incomplete, some visitors will see:

“Your connection is not private” in Chrome
“Your connection is not secure” in Firefox

In the SSL checker report:

look for mentions of intermediate certificates or chain,
check whether the tool says the chain is incomplete or missing.

If the chain is not correct:

Log in to your hosting control panel or server.
Download the correct CA bundle from your SSL provider.
Install the CA bundle together with your main certificate.

Your hosting documentation usually has a section called something like “How to install intermediate certificates / CA bundle”.

Step 6: What happens if no SSL certificate is installed at all

In some cases there is simply no certificate for your domain. When that happens, the web server often falls back to:

the first virtual host on the server, or
a default system domain belonging to your hosting provider.

The visitor then sees a certificate that does not match your domain, and the browser shows a warning.

In the SSL checker, this looks like:

certificate issued for another domain entirely, or
a message that your domain does not have a valid certificate.

To fix this:

issue a new SSL certificate for your domain, or
enable the free certificate from your hosting provider (for example, Let’s Encrypt),
then rerun the SSL check to confirm it works.

After you find the problem: how to fix it in practice

When the SSL report shows an error or a warning:

Identify which category it belongs to:
- wrong or missing hostname,
- expired certificate,
- missing CA chain,
- wrong redirect or wrong server.
Fix the configuration:
- reissue or renew the certificate,
- install the correct CA bundle,
- adjust DNS and redirects so the domain points to the right host.
Run the SSL check again to confirm that:
- all checks are green,
- the certificate matches your domain,
- the certificate chain is complete.

If you are not comfortable doing this yourself, send the SSL report to your hosting support and ask them to fix the HTTPS configuration for your domain.

Quick answer:

The “Your connection is not private / secure” warning on your own website usually means a broken HTTPS configuration: a wrong or missing SSL certificate, expired certificate, or incomplete CA chain. Use an online SSL checker, verify that the certificate matches your domain and that the full certificate chain is installed, then fix DNS, redirects, and the certificate setup on your server.

The post Fix SSL “Your connection is not private” first appeared on Valcheff Net.