Buy

Server

Premium

To upload, Pages needs SFTP access to your webspace or server. You enter the details in the Publish website dialog under Upload to a server. Pages remembers them per website and fills them in again next time. Everything in this chapter is included from the Personal package on.

What you do here

Layout of the form

From top to bottom:

  1. The note Pages fully checks the website first and then uploads it via SFTP into your host's web folder. Pages never deletes other files.
  2. Saved server from WebDonkey with Manage, only when Pages is connected to WebDonkey.
  3. Server and Port, below them User.
  4. Sign-in with Password or SSH key; for a key, the SSH key on this Mac selection.
  5. The field for password or passphrase.
  6. Web folder on the server with Browse ….
  7. Remember password encrypted on this Mac.
  8. Test connection with the result below it, if needed the fingerprint question and Prepare server.
  9. Check and publish.

Host or your own server

  • Webspace at a host: the host runs the web server. You only need the SFTP access and the web folder the host set up for your domain.
  • Your own server without a web server: on a fresh Debian or Ubuntu server, Prepare server sets up the web server, web folder and HTTPS for you.

Free and Premium

Everything in this chapter is included from the Personal package on. Choosing servers saved in WebDonkey also needs WebDonkey Premium. In Free you export the website as a ZIP.

Server access Premium

The access tells Pages where to put the website and how to sign in there. You find the details in your host's control panel, usually under SFTP, SSH or FTP accounts. Pages remembers the access per website, so everything is filled in the next time you publish.

Where to find it

Click Publish in the title bar and choose Upload to a server. The form is right below.

How to do it

  1. Under Server, enter your server's address; under Port, usually 22.
  2. Under User, enter your SFTP or SSH user.
  3. Under Sign-in, choose Password or SSH key and enter the password or key.
  4. Enter the Web folder on the server or pick it with Browse … (Choose the web folder).
  5. Check the access with Test connection (Test connection).

Fields and options

Field Content
Server The server's address without https:// and without a path, for example sftp.example.com. An IP address works too.
Port Default 22, as with most hosts.
User Your SFTP or SSH user.
Sign-in Password (default) or SSH key. Switching empties the password or passphrase field.
SSH key on this Mac Only with SSH key: the file of your private key.
Password or Key passphrase (if you set one) Depending on the sign-in. Once one is saved, the field is called Password (saved, leave empty) or Passphrase (saved, leave empty).
Web folder on the server The folder your host set up for the domain, for example html/meine-domain. A path without a leading / starts in your login folder.
Remember password encrypted on this Mac On by default. With a key it reads Remember passphrase encrypted on this Mac.

Below the web folder there is a note: as long as the access is incomplete, First enter server, user and password or key, then you can choose the web folder on the server., afterwards On your own server without a web server, Pages fills in the folder itself after "Prepare server".

With an SSH key

  1. Set Sign-in to SSH key.
  2. Under SSH key on this Mac, choose a key from your ~/.ssh folder. The list shows the private keys, that is the files without .pub at the end.
  3. If the key is somewhere else, choose Other file …. The file dialog opens in ~/.ssh.
  4. If the key is protected by a passphrase, enter it. Without a passphrase, leave the field empty.

Your provider must have the public part of the key (the .pub file) stored for your user. If there is no key in ~/.ssh, it says There is no key in your ~/.ssh folder. Choose the file that belongs to the key you added at your provider.

Saved server from WebDonkey

If Pages is connected to WebDonkey and WebDonkey is running, Saved server from WebDonkey sits above the fields. If you choose a server there, Pages fills in server, port, user and sign-in; you enter the password here. How that works and how to manage these servers is described in Saved servers from WebDonkey.

Password and passphrase

  • With Remember password encrypted on this Mac, Pages stores the password encrypted in its own data on this Mac, not in the Keychain.
  • A remembered password only applies to exactly the server you saved it for: same server, port and user. If you enter a different server, type the password again, otherwise Pages reports Please enter the password.
  • If you switch servers without a new password, for example with a key without passphrase, Pages forgets the old one.
  • If you enter a password and untick the box, Pages deletes a previously remembered password for this website.
  • Passwords and passphrases never go into the website's folder or into a backup.

What Pages remembers

For each website, Pages remembers server, port, user, sign-in, key file and web folder. It saves them as soon as you test, browse for a folder or publish, and fills them in again the next time you open the dialog.

Troubleshooting

What you see What to do
Please enter the password. The remembered password belongs to another server. Enter the password.
Please choose your SSH key. Choose a file under SSH key on this Mac.
Test connection and Browse … are greyed out. Enter server, user and password or key.
Sign-in or connection fails The messages and what they mean are listed under Common messages.

See also

Choose the web folder Premium

The web folder is the folder on the server from which the web server delivers your domain, often called the document root. Instead of typing it, you pick it right on the server with Browse … or create it there. Pages tells you whether this website or another one already sits in a folder.

Where to find it

In the Publish website dialog, Upload to a server route, the Browse … button sits next to the Web folder on the server field. It is active as soon as Server, User and password or key are filled in and Pages isn't busy.

How to do it

  1. Enter the access (Server access).
  2. Click Browse …. The form is replaced by Choose web folder with the note Choose the folder your host set up for the domain. It is often named after the domain.
  3. Pages connects and shows the web folder you entered or, if none is entered, your login folder.
  4. Click a folder to open it. .. (One level up) takes you back; the path bar jumps straight to a higher level.
  5. Read the note below the list. It tells you whether a website already sits there.
  6. Click Use this folder. The button shows the name of the folder shown. Pages enters the path in the Web folder on the server field and returns to the form.

Back at the top right returns to the form without changes.

Creating a new folder

  1. Open the folder the new one should go into.
  2. Click New folder. A field Name of the new folder appears.
  3. Type the name, for example that of your domain, and click Create.
  4. Pages creates the folder on the server and opens it. Use this folder takes it over.

Cancel closes the field again.

What the view shows

Element Meaning
Path bar The folder shown, every level clickable. With long paths, the end stays visible.
Reload The icon with the arrows reads the folder again.
New folder Creates a subfolder in the folder shown.
List The subfolders, alphabetically. Pages doesn't show files and hidden folders whose name starts with a dot. If there are none, it says There are no subfolders here.
Use this folder Takes the folder shown as the web folder.

The notes below the list

Note Meaning
This website is already here. When publishing, Pages brings it up to date. Pages recognises its own website, also after an import, from another Mac or after uploading a ZIP.
Another website … published with Pages is already here. Pages does not overwrite it without asking. Instead of the dots, name and domain of the other website appear. When uploading, Pages asks whether it may move its files aside.
This is your login folder. If other files or domains are already here, open your domain's folder or create a new one. Pages only publishes into your login folder or the server's root if nothing foreign sits there.
This folder is not empty. Before the first upload, Pages asks whether it may move the existing files into a backup folder. For example an old website. See Upload to a server.
The folder … no longer exists on the server. Pages shows you your login folder. The web folder you entered is missing. Choose another one or create it again.

Start folder from WebDonkey

If you choose a saved server from WebDonkey that has a start folder set in WebDonkey, Pages enters it as a suggestion while the Web folder on the server field is still empty.

What happens in the background

Pages signs in via SFTP with your access and only reads folder lists. It changes nothing on the server unless you create an empty folder with Create. Pages remembers the access for this website at the same time. If Pages doesn't know the server yet, the view returns to the form and asks for the fingerprint. After confirming, click Browse … again.

Free and Premium

Choosing the folder is part of uploading to a server and is included from the Personal package on.

Troubleshooting

What you see What to do
Browse … is greyed out. Enter server, user and password or key.
Your user may not open the folder … Go one level up and choose a folder that belongs to you.
The name must not be empty or contain a slash. Give the new folder a name without /.
Your user may not write to the folder … Choose a folder that belongs to you, or let Pages prepare the server. You can't create a folder here. Choose a folder that belongs to you.
A message about sign-in or connection See Common messages.

See also

Saved servers from WebDonkey Premium

If you already saved your servers in WebDonkey, you don't have to type the access in Pages again. You pick the server from the list, Pages fills in the fields, and you enter the password yourself. With Manage you add, change, test and delete servers in WebDonkey without leaving Pages.

Requirements

  • A Pages package from Personal on, because the selection belongs to the Upload to a server route.
  • Pages is connected to WebDonkey, the top right shows With WebDonkey (With and without WebDonkey), and WebDonkey is running.
  • WebDonkey Premium, because saved servers are a Premium feature in WebDonkey.
  • For Manage, an up-to-date WebDonkey.

If something is missing, one of these notes appears in this spot:

Note What is missing
While WebDonkey is running, you can choose a server saved there. WebDonkey isn't running.
With WebDonkey Premium, the servers you saved in WebDonkey are available here. WebDonkey has no Premium.
Update WebDonkey to choose the servers you saved there. WebDonkey is too old for the selection.
Update WebDonkey to add, edit and test servers here as well. The selection works, but WebDonkey is too old for Manage.

Without WebDonkey on this Mac, the section is missing entirely. Then you enter the access by hand (Server access).

Choosing a server

  1. Click Publish in the title bar and choose Upload to a server.
  2. Under Saved server from WebDonkey, open the Choose server … selection.
  3. Choose a server. The list shows name, user and server, for example "Client server (deploy@example.com)". Servers you marked red in WebDonkey carry the addition production.
  4. Pages fills in Server, Port, User and Sign-in, and for a key also the key file. If the server has a start folder in WebDonkey and the web folder is still empty, Pages enters it as a suggestion.
  5. Enter the password or the key's passphrase. WebDonkey doesn't pass it on to Pages.
  6. Continue as usual with Test connection and Check and publish.

A note below the selection says what comes from WebDonkey, for example Server, port, user and sign-in come from WebDonkey. Enter the password here, WebDonkey does not pass it on.

Good to know

  • If you then change Server, Port or User by hand, the selection no longer applies. If your access matches a saved server, the selection shows it by itself.
  • Servers Pages can't use this way appear greyed out in the list, followed by the reason: no host set, no username set or unknown sign-in method. Edit them via Manage or in WebDonkey.
  • If WebDonkey signs in through the SSH agent, Pages switches to SSH key and shows WebDonkey signs in to this server through the SSH agent. Pages needs the key file: choose it below.
  • If the key file from WebDonkey isn't on this Mac, it says The key file from WebDonkey is not on this Mac. Choose it below.
  • If you haven't saved a server in WebDonkey yet, it says No connections yet.

Managing servers

  1. Next to Saved server from WebDonkey, click Manage. The form is replaced by Servers in WebDonkey with the note WebDonkey stores these connections. What you add, change or delete here also applies in WebDonkey. Start folder, colour mark and project are set in WebDonkey under Remote.
  2. Each row shows the name (red-marked ones with production), below it user, server and port and the sign-in method.
  3. On the right are three icons: Test connection (plug), Edit (pencil) and Delete (bin).
  4. At the bottom, New connection adds a server.
  5. Back returns to the form. After every save or delete, Pages reloads the list.

Servers that Pages can't use carry the note not usable in Pages: … with the reason here.

Testing

Clicking the plug makes WebDonkey sign in to the server, with the password or key stored there. If it works, it says Connected: WebDonkey signed in to the server. Otherwise WebDonkey's message appears, for example Login failed or The server did not answer in time. Servers with the note not usable in Pages can't be tested.

Adding and editing

New connection or the pencil opens a form like the one you know from WebDonkey:

Field Meaning
Name Required. This is the server's name in the selection.
Host Required. The server's address.
Port Default 22.
Username Required.
Authentication Password, SSH key or SSH agent.
Private key file Only with SSH key: choose from ~/.ssh or Browse.
Agent socket (optional) Only with SSH agent; may stay empty.
Password or Key passphrase When editing, empty means Leave blank to keep the stored secret. The eye shows what you typed (Show, Hide).

At the bottom are Test connection (checks the values you entered without saving), Cancel and Save. Save is active as soon as name, host and username are filled in.

A new server instead of a move

If you change Host, Port or Username while editing, it is usually a new server, for example after switching hosts. Then the checkbox Save as new server appears, ticked by default:

  • Ticked: Pages adds a new connection in WebDonkey. The existing one stays as it is, with everything WebDonkey links to it, such as backups, syncs and databases. With password sign-in it then says Enter the server password for this., and Save stays greyed out until you have entered it.
  • Unticked: Pages changes the existing connection, in WebDonkey as well. What WebDonkey links to it then goes to the new server. If WebDonkey still uses the connection for something, it refuses new values for host, port and user and recommends Save as new server.

Deleting

  1. Click the bin.
  2. The row shows Delete the connection "…"? with Cancel and Delete connection.
  3. Click Delete connection.

If something in WebDonkey still depends on the connection, such as backups, syncs, databases or scheduled tasks, it can't be deleted. The message names what depends on it. Remove that in WebDonkey first.

What happens in the background

Pages only talks locally on this Mac to the running WebDonkey. From WebDonkey, Pages receives name, address, port, user, sign-in method, key file, start folder and colour mark for each server, never a password or passphrase. Everything is saved in WebDonkey only. Pages itself only remembers the access you use for a website, just as with manual entry.

Free and Premium

  • In Pages, the selection and managing belong to uploading to a server, so they are included from the Personal package on.
  • In WebDonkey, saved servers are part of Premium. Without Premium, managing reports Saved servers are part of WebDonkey Premium.

Troubleshooting

What you see What to do
WebDonkey is not running. Start WebDonkey and try again. Start WebDonkey.
WebDonkey is not answering right now. Please try again in a moment. Wait a moment and try again.
Your WebDonkey cannot manage servers from Pages yet. Please update WebDonkey. Update WebDonkey.
WebDonkey did not accept this. Check WebDonkey under Remote. Open WebDonkey and look at the connection under Remote.
The saved password can no longer be read … Edit the connection and enter the password again.
The connection no longer exists. Close the dialog and open it again; Pages then reloads the list.

See also

Test connection Premium

Test connection signs in to the server and checks the web folder without uploading anything. On servers with shell access, Pages also looks whether a web server is running. That way you know before the first publish whether everything fits, and if needed you get the offer to prepare the server.

Where to find it

In the Publish website dialog, Upload to a server route, below the access fields. Next to it: Checks access and web folder without uploading anything.

How to do it

  1. Enter Server, User and password or key, ideally the web folder too (Server access).
  2. Click Test connection. The button is active as soon as the access details are complete and Pages isn't busy.
  3. If Pages doesn't know the server yet, it first asks for its fingerprint. After Trust server and connect, the test continues by itself.
  4. The result appears as a short list below the button.

The result

Line Meaning
Connected to … as … Sign-in worked, with operating system and user.
Connected, file transfer only. Sign-in worked, but the account only allows SFTP and no commands. Uploading works, setting up doesn't.
Web folder … found, Pages may write there. Everything is ready to upload.
No web folder entered yet. Enter a web folder or pick it with Browse … (Choose the web folder).
The web folder … does not exist yet. Choose an existing folder, create it or let Pages prepare the server.
Your user may not write to the web folder … Choose a folder that belongs to you, or let Pages prepare the server.
Web server is running (…). A web server runs on the server; its name is in brackets.
No web server is running on the server yet. Without a web server, the website can't be seen after uploading.

The web server lines only appear for accounts that allow more than file transfer.

Offering to prepare the server

If no web server is running yet, the web folder is missing or your user may not write there, the Prepare server box appears below the result (Prepare server). If this server can't be set up, the reason appears there instead, for example A web server is already running on the server. Pages does not change it: enter the web folder it serves for your domain.

If Pages has already set up the server, a line such as Pages set up this server for … with HTTPS. appears with the Set up again button. If the Web folder on the server field is still empty then, Pages enters the folder it set up.

What happens in the background

Pages signs in via SFTP and looks in the web folder whether it exists and whether it may write there. With shell access, it reads a few details about the system, such as operating system, running web servers and whether your user may install programs. Pages changes nothing on the server while doing so. Pages remembers the access for this website, a password only when the remember box is ticked.

If you then change server, port, user, sign-in, key or password, the result expires. Test again then.

Free and Premium

Test connection is included from the Personal package on.

Troubleshooting

Instead of the list, a red message appears, for example User name or password is wrong. or The server does not answer. Check address and port or the firewall at your provider. All messages and what to do are listed under Common messages.

See also

Server fingerprint Premium

Every server identifies itself with a key of its own. So that nobody can get between you and your server, Pages remembers the fingerprint of that key on the first connection and compares it on every later one. If Pages doesn't know a server yet or it identifies itself differently than before, Pages asks you before it sends a password or key at all.

When the question comes

On the first connection to a server, whether through Test connection, Browse … or Check and publish. The question appears in the form below Test connection. If it came while browsing, the view returns to the form for it.

New server

  1. Pages shows New server with a note that it is connecting to this server for the first time.
  2. Below it, Fingerprint: shows a string starting with SHA256: and the key type in brackets.
  3. If your provider shows the fingerprint, for example in the server panel, compare the two.
  4. Click Trust server and connect. Pages remembers the fingerprint and tests the connection by itself.

If the question came while publishing or browsing, start that step again afterwards.

Changed fingerprint

If a known server identifies itself with a different key, Pages warns in red: Warning: the server identifies itself differently than last time, with the previous fingerprint under Before: and the new one under Now:.

  • If the server was reinstalled or moved, this is normal. Then click Server was reinstalled, accept the new fingerprint.
  • If not, don't connect and ask your provider. Someone could have got in between.

As long as you haven't confirmed the fingerprint, Pages uploads nothing.

What happens in the background

Pages stores the fingerprint per server and port in its own data on this Mac. It applies to all websites that use this server. Pages neither reads nor changes the ~/.ssh/known_hosts file for this.

Free and Premium

Part of uploading to a server, included from the Personal package on.

Troubleshooting

  • The fingerprint is not valid. Please test the connection again. Click Test connection again.
  • You are unsure whether the new fingerprint is right: don't confirm it and ask your provider first.

See also

Prepare server Premium

A fresh server of your own has no web server running yet, so your website wouldn't be visible after uploading. Prepare server sets it up for you: web server, web folder and HTTPS for your domain. This works on Debian and Ubuntu servers you can sign in to via SSH with shell access.

Where to find it

In the Publish website dialog, Upload to a server route: click Test connection. If no web server is running yet, the web folder is missing or your user may not write there, the Prepare server box appears below it (Test connection).

How to do it

  1. Enter the access and click Test connection.
  2. Read the plan in the Prepare server box. It is shown in plain words; nothing starts until you click.
  3. If your user needs a password for the setup, the sudo password field appears. Usually it is the same as for signing in. Pages uses it only for this setup and doesn't save it.
  4. Click Set up server now. This usually takes one to three minutes. Each step shows whether it is running or done; the title bar shows Setting up server ….
  5. At the end it says Your server is ready, with HTTPS. Web folder: … or Your server is ready, HTTP only for now. Web folder: …, below it a link to the website's address.
  6. Pages enters the web folder under Web folder on the server. Now you can Check and publish.

If you want to quit Pages during the setup, it asks first (Question when quitting).

The plan

Depending on the server, Pages shows these steps:

  1. Update package sources and install basic tools.
  2. Install the Caddy web server from the official Caddy package source. If Caddy is already there, this step is skipped.
  3. Create the web folder, owned by your user, under /var/www/ with the name of your domain (without a domain, the name of the website's folder) and /public after it.
  4. Configure the web server securely: no folder listings, hidden files blocked, security headers.
  5. HTTPS for your domain: Caddy gets the certificate for free from Let's Encrypt and renews it by itself. The terms of Let's Encrypt apply. If the domain doesn't fit yet, this step reads HTTP only for now, so without encryption.
  6. Open ports 80 and 443 if a firewall is active. SSH access stays as it is.
  7. Start and check the web server.

Under Technical details: what Pages runs on the server you find the commands if you want to see them.

What Pages changes on the server

  • Pages doesn't replace an existing Caddy configuration. It adds a file of its own per website.
  • Pages checks every new setting before it applies. If it isn't valid, Pages restores the previous state.
  • Pages never switches on a firewall itself. If one is active, it only opens ports 80 and 443.
  • The setup can be repeated; a second run doesn't break anything.

HTTPS and domain

The server only gets HTTPS once your domain points to it. Pages checks this beforehand and says in the plan what is missing:

  • If the website has no domain yet, the server shows it without encryption under its IP address for now.
  • If the domain doesn't point to any server, enter your server's IP address at your domain provider (A record).
  • If the domain points to a different server, Pages names both addresses. Change the record at your domain provider.

Afterwards set up the server once more with Set up again to get HTTPS. You find the button after Test connection in the line Pages set up this server, so far with HTTP only. …. Your website and other settings are kept.

When Pages doesn't set up

The plan is then replaced by the reason:

  • Pages doesn't set up systems other than Debian and Ubuntu. Uploading into an existing web folder still works.
  • If another web server is already running, Pages doesn't change it. Enter the web folder it serves for your domain.
  • If your user may not install programs (no sudo), sign in as root once.
  • An account for file transfer only isn't enough for the setup. The box doesn't appear at all then.

Notes after the setup

  • Contact form: Pages doesn't set up mail sending on the server yet. Without it, the form can't send messages there, and visitors see an error when sending.
  • First certificate: if the address doesn't answer yet, the first certificate can take a few minutes. If it stays that way, check that the firewall at your provider lets ports 80 and 443 through.
  • Further addresses: if another address of your website doesn't point to this server, for example the version with or without www, Pages says so as well. Visitors using that address wouldn't reach your website otherwise.

Free and Premium

Prepare server is included from the Personal package on.

Troubleshooting

The messages during setup are listed under Common messages. After an error the box also shows Technical details with the server's output. They help support.

See also

Common messages Premium

When testing, browsing, publishing and preparing, Pages states the reason in plain words. Here are the most common messages, sorted by the step in which they appear, with what to do. Where a message shows "…", Pages fills in a folder, a number or a name.

Access and sign-in

Message What to do
Server, user and a password or key are needed. Fill in the missing fields.
The server address is not valid. Enter it without https:// and without a path, for example server.example.com. Enter only the server's name or IP address.
The port must be a number between 1 and 65535. Usually it is 22. Correct the port.
This server does not exist. Please check the address. Check the spelling of the address.
The server does not accept connections on this port. Check the port, usually it is 22. If in doubt, ask your provider for the SFTP port.
The server does not answer. Check address and port or the firewall at your provider. Check address and port. If the provider's firewall doesn't let the port through, open it there.
User name or password is wrong. Check both in your host's control panel.
The server does not accept this key for this user. Check user and key. Store the public key with your provider or choose the matching one.
Pages cannot read the key file. Please choose it again. Choose the file under SSH key on this Mac again.
This file is not an SSH key Pages can read. Choose the private key file, the one without .pub at the end. Choose the file without .pub.
Your key is protected by a passphrase. Please enter it. Enter the passphrase.
The passphrase does not match this key. Check the passphrase.
The server does not allow SFTP for this account. Ask your provider for SFTP access. Have your provider set up SFTP access for you.
The server closed the connection. Please try again. Try again.
Connecting to the server failed. Please try again. Try again; otherwise check address and access.
Please enter the password. The remembered password belongs to another server. Enter it.
Pages does not know this server yet. Please confirm its fingerprint. Confirm the fingerprint.
The server presents a different key than last time. See Changed fingerprint.

Web folder

Message What to do
Please choose the web folder on the server. Enter a web folder or pick it with Browse ….
The web folder … does not exist on the server. Under "Browse …", choose the folder your host set up for the domain, or let Pages prepare the server. Find the right folder (Choose the web folder).
Your user may not write to the folder … Choose a folder that belongs to you, or let Pages prepare the server. Choose a folder of your own.
Your user may not open the folder … Appears while browsing. Choose another folder.
The name must not be empty or contain a slash. Give the new folder a valid name.
The folder … is the root of the server or your login folder, and it already contains other files or folders, for example further domains. Pages does not publish here. … Under Browse …, create a subfolder for the website and choose it as the web folder.
The web folder already contains … other files, for example an old website. Pages can move them into a hidden backup folder: agree below or choose an empty folder. Tick the box below it and start again, or choose an empty folder (Upload to a server).
The web folder already contains another website … published with Pages. Pages does not overwrite it without asking: … Agree and Pages moves its files aside, or choose a different folder.
The server has no free space left. Free up space or ask your provider for more storage.

Publishing

Message What to do
Not ready to publish yet: … The reason follows, for example the summary of the check (What must be ready first).
Uploading failed. Please try again. Try again. Pages cleans up the leftovers of the interrupted run while doing so.
The website data is not valid. Have the website repaired in the chat or go back with Undo.
Publishing directly is included from the Personal package on. Activate a package or export as a ZIP.
The settings for the contact form (.env) could not be created. The form only sends once they exist. Check the permissions in the folder above the web folder and publish again.

Prepare server

Message What to do
Pages needs your sudo password for the setup. Enter the sudo password.
The sudo password is wrong. Check the password; usually it is your sign-in password.
Your user may not install programs on the server. Sign in as root once or ask your provider. Sign in as root for the setup.
This account only allows file transfer. Pages cannot set up the server with it. Ask your provider for SSH access with a shell.
Pages only sets up Debian and Ubuntu servers. Uploading into an existing web folder still works.
Another web server is already running on the server. Pages does not change it. Enter the web folder that web server serves.
The server cannot reach the internet to download programs. Check its internet connection and try again. Check the server's network settings.
The basic packages could not be installed. Please try again in a few minutes. Wait a few minutes and try again.
The Caddy web server could not be installed. Please try again in a few minutes. Try again later.
The new web server settings were not valid. Pages restored the previous state. The previous state is restored. Contact support with the content under Technical details.
The web server does not start. The technical details below help support. Send the content under Technical details to support.
Something changed on the server since the check. Please look at the plan again and then start once more. Read the new plan and start again.
The setup did not finish. Please try again. Try again.

See also

Cookie preferences

This website uses cookies to ensure the best experience possible. Your choice applies to webdonkey.io and the shop at shop.webdonkey.io. More information...

Technically required

Cookies required for this website to function:

Always on
WebDonkey
WebDonkey
Provider: BuI Hinsche GmbH, Neumarkt 7, 06712 Zeitz, Germany
Purpose: Your consent, colour scheme and language for website and shop, price switches; with wd_debug in the address, the measurement events in the developer console for troubleshooting
Cookies and storage: Cookie wd_consent on .webdonkey.io, shared with shop.webdonkey.io (12 months); cookies wd_theme and wd_lang on .webdonkey.io, shared with shop.webdonkey.io, only when you switch colour scheme or language yourself (365 days); localStorage wd:consent, wd:theme, wd:lang; sessionStorage wd:acc, wd:term, wd:debug (only with wd_debug in the address; until the tab closes)

Statistics

Shows us which pages and products people look at on webdonkey.io and in the shop, where visitors come from and how they get to a purchase (with order number, amount and products, without name or email address). Provider: Google. Transfer to the USA possible (EU-US Data Privacy Framework). Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Google Analytics 4
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Google Analytics 4
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Usage statistics: page views, clicks, scroll depth, sources, devices, load times; in the shop also basket, checkout, purchases, registration and sign-in
Cookies and storage: _ga, _ga_<ID> (2 years)
Privacy policy

Marketing

Measures whether our ads on Facebook, Instagram and TikTok lead to visits and downloads on webdonkey.io and to registrations and purchases in the shop, and builds audiences for ads. Providers: Meta and TikTok, with whom we are jointly responsible for this. With this consent Google may also set advertising cookies (_gcl_…). Transfer to the USA and other countries outside the EU possible. Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Meta Pixel (Facebook, Instagram), TikTok Pixel
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Meta Pixel (Facebook, Instagram)
Provider: Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland
Purpose: Ad measurement and target groups on Facebook and Instagram, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _fbp (3 months), _fbc (3 months, only if you arrive through an ad), fr on facebook.com (3 months)
Privacy policy
TikTok Pixel
Provider: TikTok Technology Limited, 10 Earlsfort Terrace, Dublin, D02 T380, Ireland
Purpose: Ad measurement and target groups on TikTok, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _ttp, _tt_enable_cookie (13 months)
Privacy policy