Can EnderDash upload custom JARs to Aternos?

Lots of Minecraft hosts make server setup easy until you need one thing outside their normal catalog.

Maybe you want a custom Paper fork, a private plugin, a mod that is not listed yet, or a quick Linux shell so you can inspect the server directory directly. That is exactly the kind of admin work EnderDash is meant to make less annoying on servers you control.

But there is an important boundary: EnderDash is not a way to bypass a host's rules.

Quick answer

EnderDash can help with custom JARs, file management, and host shell access when your host allows you to install the EnderDash agent or run the standalone host agent. On Aternos' free service, the answer is no: Aternos does not offer FTP or full plugin and mod upload access, and EnderDash should not be used as a workaround for that restriction.

What Aternos allows today

This post was last checked on May 1, 2026. Aternos' own help center says that the free service does not provide FTP access or full file upload capabilities for plugins and mods. Their explanation points to service fairness and security: custom plugin and mod uploads could be abused to keep free servers running continuously, and custom code could include harmful software.

Aternos does still support many normal customization paths:

plugins from the Aternos plugin catalog
mods from the Aternos mod catalog
supported mod loaders such as Forge, Fabric, NeoForge, and Quilt
datapacks
resource packs
Bedrock add-ons
some configuration files and related assets

For custom plugin, mod, or modpack uploads, Aternos' current recommendation is exaroton, its paid hosting platform with full file access.

Sources:

What EnderDash can and cannot do

EnderDash works by running an agent on the server, proxy, or host you want to manage. The dashboard can only show panels for capabilities the connected target actually exposes, and your role and plan still have to allow those actions.

That means the setup model is simple, but not magic:

If you can install the EnderDash plugin on a Bukkit, Spigot, Paper, Purpur, Folia, Velocity, or BungeeCord runtime, EnderDash can connect to that runtime.
If you can run the standalone EnderDash agent on a Linux host, EnderDash can expose host-level tools such as files, processes, services, and shell access when the environment allows them.
If your host does not let you upload the agent, run a standalone process, or use shell access, EnderDash cannot create that access from the outside.

That last point matters for Aternos. If a provider's policy says you cannot upload arbitrary plugin or mod JARs and cannot use FTP or shell access, the right answer is not to route around the policy. Use the supported catalog, ask the provider to add the plugin or mod, move to a plan that allows custom uploads, or use a host where you have the access you need.

When EnderDash is a good fit

EnderDash is useful when the host restriction is a convenience gap, not a permission boundary.

For example, it can fit well when:

you run a VPS, dedicated server, home server, or colocated machine
your Minecraft host allows plugin uploads but its panel file manager is clumsy
your host lets you run a separate Java process or startup command for a standalone agent
your team needs a shared file manager, console, and shell workflow without handing everyone raw SSH credentials
you manage servers across more than one provider and want the same operating surface everywhere

It is not a fit when:

the provider does not allow the EnderDash agent
the provider forbids arbitrary plugin or mod uploads
you are trying to get a Linux shell on infrastructure you are not allowed to administer
the provider's terms or support docs say a workflow is not permitted

What the setup looks like on a compatible host

On a host that allows it, the flow is straightforward.

Confirm the host allows the agent

Check the host's rules first. You need one of these:

permission to upload the EnderDash plugin JAR into plugins/
permission to run the standalone EnderDash agent beside the server
a host-provided plugin catalog that includes EnderDash

If the answer is no, stop there. EnderDash will not be the right path for that host.

Install the matching EnderDash agent

In EnderDash, create or open the server record, then download the agent that matches the target runtime.

Target	Agent
Bukkit, Spigot, Paper, Purpur, Folia	`EnderDash-Bukkit.jar`
Velocity	`EnderDash-Velocity.jar`
BungeeCord or Waterfall	`EnderDash-Bungeecord.jar`
Standalone host runtime	`EnderDash-Standalone.jar`

Plugin and proxy agents usually go in plugins/. Standalone agents run as their own process on the host.

Register the agent key

Restart the target so the agent loads. Then register the server's agent key.

For plugin and proxy runtimes, run this from the runtime console:

enderdash install <agentKey>

For standalone host agents, save the key in the standalone config and start the agent.

Use Files for custom JAR work

Once the server is online in EnderDash, open Files if the target exposes filesystem access.

A safe custom JAR workflow usually looks like this:

Stop the server.
Back up the current JAR and config files.
Upload the new JAR to the correct directory.
Update the startup command only if the filename changed.
Start the server and watch the console for version, Java, or dependency errors.

For plugin and mod JARs, the same rule applies: only upload files your host allows, and only to the directories your runtime expects.

Use Shell when the host allows it

If the connected target exposes terminal access and your plan includes host terminal access, the Shell panel can handle the small Linux tasks that usually send admins back to SSH:

java -version
ls -lah
du -sh world plugins logs

On a server you administer, that is useful for checking Java compatibility, inspecting disk usage, downloading a known server JAR from an official source, or moving files into place. On a restricted managed host, do not treat shell access as a loophole around the provider's rules.

A practical host compatibility table

Host situation	EnderDash fit	What to do
Aternos free server	Not for custom uploads or shell access	Use Aternos' supported plugin, mod, datapack, and resource-pack flows.
exaroton or another host with full file access	Good fit if the agent can run	Install the agent and use EnderDash as the shared operating surface.
Managed Minecraft host with plugin uploads but no native custom server JAR upload	Often a fit	Install the plugin agent if permitted, then use allowed file workflows inside the server directory.
VPS, dedicated machine, or home server	Strong fit	Use the standalone host agent or the Minecraft runtime agent, depending on how much host access you want.
Host with no custom plugins, no standalone process, and no shell	Not a fit	Pick a supported catalog option or move to a host that gives you the access you need.

Safer options if you are currently on Aternos

If you are on Aternos and need something outside the catalog, start with the supported paths:

Search the Aternos plugin, mod, or modpack catalog first.
Use datapacks or resource packs when they can solve the problem without server-side custom code.
Suggest the missing plugin, mod, or modpack through Aternos' normal process.
Move to exaroton or another host that explicitly allows custom uploads.
Self-host on Linux if you want full control over server JARs, shell access, updates, and backups.

If you choose the self-hosting route, the setup is not as hard as it used to be, but it does make you responsible for Java versions, ports, backups, and updates. Start with How to self-host a Minecraft server on Linux with Paper, then add EnderDash with the install-agent guide in the docs.

The rule of thumb

EnderDash is an operations layer for servers you are allowed to manage.

If the host gives you legitimate access to install the agent, upload files, or run a shell, EnderDash can make that work cleaner and easier for the whole team. If the host intentionally withholds that access, EnderDash is not the workaround. At that point the clean answer is to use the host's supported catalog, upgrade to a plan with full file access, or move the server somewhere that matches the control you need.