No, It is absolutely FREE!

Absolutely not! If you do, you will be permanently banned by the system (automatically) and will not be able to create another account.

Yes, we allow IRC access to all IRC servers and networks.

Yes, every user gets a personal vhost at <user>.users.efn.lt.

Yes, you may run background processes. More details

Yes, we allow both psyBNC and eggdrop, and you may run two psyBNC instances, two eggdrops, or psyBNC + eggdrop.

1. Check if the service is running at all (use ps ux command in the shell).
2. Ensure the port your service is bound to is within the 10000-12000 port range, as only this range is allowed.

ou need to use the SFTP/SCP protocol. For Windows, use WinSCP for simple file uploads.

For general discussion and questions about shell commands and usage, please ask in our IRC or Telegram channels. Please DO NOT Private Message administrators without a serious reason!

1. If you can’t connect and receive errors like “Operation not permitted” (irssi), “(Address invalid on remote machine) NO SERVERS WILL ACCEPT MY CONNECTION” (eggdrop), or similar with psyBNC, it means you have reached the TCP connection limit. Free shell users are limited to 4 TCP connections. If you attempt too many connections quickly, this limit may be exceeded. To resolve, kill all running processes, wait a few minutes (5 minutes should be enough), and try again.
2. If you receive a “many connections from this host” error from the server you’re connecting to, it means other users are also connecting from our free shell server using the same IPv4 address. To resolve, request that IRC server/network operators create an I-line exception for our free shell service’s IPv4 address to allow more sessions.
3. NOTE! Before reporting a problem, check that your service (e.g., eggdrop, psyBNC) is writing logs. When reporting any issue, please do so in the IRC or Telegram channel.

PsyBNC logs can be found in psybnc/logs directory.

To enable eggdrop logging, add the following line to your configuration file::

logfile dhmcors * "logs/eggdrop.log"

• If you receive a timeout when connecting, it means you have been temporarily banned after entering the wrong password multiple times. For security, the system temporarily bans users who enter the wrong password three times for 10 minutes. After this period, the ban is lifted automatically.
• If you receive “access denied,” this usually means you entered an incorrect username or password. Use the right-click option to paste your username/password into PuTTY, as both are case-sensitive. Ensure you copy and paste exactly as they appear.

If you found that your process, binary, or script was killed and renamed to binary_too_much_cpu_time, please read below.

Starting from 2025-11-08, a new feature has been introduced. From now on, resource-hungry processes — especially those that continuously consume 100% CPU for more than 60 minutes — will be automatically terminated and renamed. This mechanism helps prevent malicious or poorly written user programs from exhausting system resources and negatively affecting other users. If you plan to run legitimate high-CPU applications, exceptions can be made, but you must first contact us to discuss it. Please be prepared to explain why you need this application, what it does, and how it operates.

If you lose your password, there is no quick way to reset or restore it. We use a non-standard centralized authentication system, so password resets take time. To request a password reset, please be prepared to donate $5 to support our project. If you have already donated, please contact the system administrator.

Some regions generate a disproportionately high amount of abusive traffic, automated usage, limit bypassing, and other activity that increases our server, bandwidth, electricity, and maintenance costs.

At the same time, donation support from these regions has been extremely low, despite heavy use of the service. We cannot continue paying for unlimited free access where usage creates significant costs but almost no financial support.

Country-level blocking is not ideal, and we know legitimate users may be affected. However, blocking individual users is often ineffective because abusive users rotate IP addresses, use VPNs, and create new accounts.

These restrictions are based on traffic, abuse levels, operational costs, and donation data—not ethnicity or nationality. Supporters may contact us to request access.