http://wiki.folk.zone/ 2026-06-21T14:23:59+00:00 http://wiki.folk.zone/ http://wiki.folk.zone/lib/exe/fetch.php?media=wiki:dokuwiki.svg text/html 2026-06-21T06:14:05+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.folk.zone/doku.php?id=folkzone:services:irc:troubleshooting:certificate_errors&rev=1782022445&do=diff Certificate Errors Symptoms TLS certificate warnings or connection failures on port 6697. Cause Self-signed certificates not trusted by clients. Fix 1. Accept self-signed certificate in IRC client 2. Or configure Let's Encrypt certificates (see Ergo documentation) 3. For testing, use port 6667 (plaintext) text/html 2026-06-21T06:14:01+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.folk.zone/doku.php?id=folkzone:services:irc:troubleshooting:config_changes_not_applied&rev=1782022441&do=diff Config Changes Not Applied Symptoms Modified ircd.yaml but changes not taking effect. Cause Config not reloaded after modification. Fix 1. Reload Ergo config: docker kill -s SIGHUP folkzone-irc-ergo 2. Verify reload: docker logs folkzone-irc-ergo --tail 10 3. Look for "Rehash completed successfully" text/html 2026-06-21T06:14:09+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.folk.zone/doku.php?id=folkzone:services:irc:troubleshooting:database_corruption&rev=1782022449&do=diff Database Corruption Symptoms Ergo fails to start with database errors. Cause Corrupted database file or improper shutdown. Fix 1. Stop containers: docker compose stop folkzone-irc-ergo 2. Backup current data if possible 3. Delete data volume: docker volume rm folkzone-new_folkzone_irc_ergo_data 4. Restart with fresh database: docker compose up -d folkzone-irc-ergo 5. Note: This will reset all accounts and channels text/html 2026-06-21T06:13:46+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.folk.zone/doku.php?id=folkzone:services:irc:troubleshooting:ergo_crashes_on_startup&rev=1782022426&do=diff Ergo Crashes on Startup Symptoms Container keeps restarting with segmentation faults or config errors. Cause Mounting custom ircd.yaml before first run, or incomplete config file. Fix 1. Remove custom ircd.yaml mount from docker-compose.yml 2. Stop containers: docker compose stop folkzone-irc-ergo folkzone-irc-lounge 3. Delete the data volume: docker volume rm folkzone-new_folkzone_irc_ergo_data 4. Restart with default config: docker compose up -d folkzone-irc-ergo folkzone-irc-lounge 5. Foll… text/html 2026-06-21T06:14:13+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.folk.zone/doku.php?id=folkzone:services:irc:troubleshooting:high_memory_usage&rev=1782022453&do=diff High Memory Usage Symptoms IRC containers using excessive memory. Cause Large history buffers or many connected users. Fix 1. Check Ergo config history settings 2. Reduce channel-length and client-length in ircd.yaml 3. Restart Ergo after changes text/html 2026-06-21T06:13:49+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.folk.zone/doku.php?id=folkzone:services:irc:troubleshooting:lounge_cannot_connect&rev=1782022429&do=diff The Lounge Cannot Connect to Ergo Symptoms The Lounge shows connection errors or cannot reach the IRC server. Cause Containers on different networks or incorrect host configuration. Fix 1. Verify both containers are on same network (folkzone_net) 2. Check The Lounge config uses Docker network name: folkzone-irc-ergo 3. Test connectivity: docker exec folkzone-irc-lounge ping folkzone-irc-ergo 4. Restart The Lounge: docker compose restart folkzone-irc-lounge text/html 2026-06-21T06:13:54+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.folk.zone/doku.php?id=folkzone:services:irc:troubleshooting:port_connection_issues&rev=1782022434&do=diff Port Connection Issues Symptoms Cannot connect to irc-direct.folk.zone:6667 or :6697 from external clients. Cause Ports not exposed, firewall blocking, or router not forwarding. Fix 1. Verify ports are exposed in docker-compose.yml 2. Check firewall allows ports 6667 and 6697 3. Test locally: nc -zv localhost 6667 4. Verify router port forwarding if connecting from outside LAN text/html 2026-06-21T06:14:19+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.folk.zone/doku.php?id=folkzone:services:irc:troubleshooting:tls_connection_issues&rev=1782022459&do=diff TLS Connection Issues (bytes remaining on stream) Symptoms IRC clients show “connection to server lost (bytes remaining on stream)” errors repeatedly. Cause Attempting to proxy IRC protocol through Caddy using HTTP-based directives. What Did Not Work text/html 2026-06-21T06:13:58+00:00 Anonymous (anonymous@undisclosed.example.com) http://wiki.folk.zone/doku.php?id=folkzone:services:irc:troubleshooting:web_client_not_loading&rev=1782022438&do=diff Web Client Not Loading Symptoms <https://irc.folk.zone> does not load or shows errors. Cause Caddy not running, reverse proxy misconfigured, or The Lounge down. Fix 1. Check Caddy status: docker compose ps caddy 2. Check The Lounge status: docker compose ps folkzone-irc-lounge 3. Restart Caddy: docker compose restart caddy 4. Verify Caddyfile has irc.folk.zone configuration 5. Check Caddy logs: docker logs folkzone-caddy