MyServer & MyDocker Lösungen nach Maß
| In unserer hochverfügbaren und leistungsstarken Infrastruktur bieten wir Server- & Docker-Lösungen mit Flexibilität und Eigenständigkeit. Du triffst alleinig die Entscheidung, was wie umgesetzt wird. In unserem Panel lassen sich Docker-Container bequem verwalten. | |
|
|
Wähle ein passendes MyServer Paket deiner Wahl
| vServer SMALL | |
|---|---|
| Starterset for your own Server with full control | |
11,99 € /Monat* |
|
| Add to cart | |
| Speicherplatz | 50 GB |
| RAM | 2 GB |
| CPU | 1 vCore |
| Setupkosten | 60 € |
| tägliche Sicherungen | |
| vServer SMALL | |
|---|---|
| xxx | |
25,19 € /Monat* |
|
| AUSWÄHLEN | |
| Speicherplatz | 200 GB |
| RAM | 8 GB |
| CPU | 4 vCore |
| Setupkosten | 60 € |
| tägliche Sicherungen | |
Alle angegebenen Preise inklusive 20% MWST
| Datenübertragungsrate (UP/DOWN) | 1000 Mbit/s | ||
| VPS/dedizierte Server | |||
| SFTP/SSH Zugang | |||
| DNS-Verwaltung | |||
| IPv6-Konnektivität | |||
| IPv4-Konnektivität | via Proxy-Server | ||
| IPv4-Adresse | gegen Aufpreis | ||
| Betriebssysteme | Ubuntu, Debian, ArchLinux | ||
| Docker Verwaltung | |||
| Abrechnung | 3 Monate im Voraus |
| Kündigungsfrist | 35 Tage bis zur Vertragsverlängerung |
| Zahlungsmodalitäten | Banküberweisung oder Paypal |
| Mindestvertragsdauer | 3 Monate |
| Verfügbarkeit | 1-2 Werktage nach Zahlungseingang |
| Jederzeit erweiterbar | |
| Serverstandort | Österreich/Wien |
| Stromherkunft | 100% Ökostrom |
| Traffic | fair-use |
| Bei Vertragsabschluss | gelten unsere AGB |
FAQ
Server/Docker
Uns ist ein faires Miteinander bei der Nutzung geteilter Ressourcen wichtig. Fair-Use bedeutet unlimitierter Datentransfer. Es existiert dennoch eine Obergrenze bei exzessiver Nutzung, wenn andere Kund:innen davon beeinträchtigt sind oder der Server dadurch überlastet ist. Der/Die Kund:in wird in diesem Fall darauf hingewiesen und es kann zu Bandbreitenlimitierungen kommen.
MyWebspace provides a simple REST API to update DNS entries automatically. This allows you to do a number of things:
- Dynamic DNS (if you are behind a dynamic IP)
- Automatic updating of TXT for Letsencrypt (if you are running your own webserver)
- Round Robin DNS for Loadbalancing / Failover (if you are running your own webservers)
The REST API can only update existing entries, not create new ones, so you have to create the entry in the my-webspace.at panel first.
Please keep in mind that the key must be kept private! With the key anyone could change your DNS records. If you think you key has been compromised, please delete the DNS entry in the my-webspace.at panel and re-create it. A new key will be provided for you.
At the moment you can use the API to update A, AAAA and TXT records. The API can be accessed via HTTPS (preferred) or plain HTTP:
| Endpoint | https | http |
|---|---|---|
| Default protocol | https://panel.my-webspace.at/dns | http://panel.my-webspace.at/dns |
| IPv4 | https://4.panel.my-webspace.at/dns | http://4.panel.my-webspace.at/dns |
| IPv6 | https://6.panel.my-webspace.at/dns | http://6.panel.my-webspace.at/dns |
You can supply the following parameters, either via GET or POST:
| Parameter | Value |
|---|---|
| key | Autoupdate-Key from the panel, mandatory to query or change DNS-records |
| a | Only for A records, IP address to set. Can use the special value "remote" to use the address the request is coming from. The address needs to be a valid IPv4 address. When using the "remote" feature the endpoint 4.panel.my-webspace.at should be used to ensure IPv4 is being used for the request and a valid IP address is returned for the record type. |
| aaaa | Only for AAAA records, IP address to set. Can use the special value "remote" to use the address the request is coming from. The address needs to be a valid IPv6 address. When using the "remote" feature the endpoint 6.panel.my-webspace.at should be used to ensure IPv6 is being used for the request and a valid IP address is returned for the record type. |
| txt | Only for TXT records, the new content of the record |
If no new record data is provided, only the existing data is returned.
The response is a JSON object with the following values:
| Key | Value |
|---|---|
| status | "error": In case of an error, more information is provided in the "error" key "unchanged": The current value was already stored in the DNS record "updated": The DNS record has been updated and the changes will be reflected in the DNS soon |
| error | Only if status == "error", the error message. One of "bad key", "key missing", "invalid A data" or "invalid AAAA data" |
| domain | The top-level domain being changed or queried |
| name | The subdomain being changed or queried |
| type | The type of the DNS record |
| data | The (new) value of the DNS record |
| remote-ip | The IP the query originated from. This is always included, even if no parameters are supplied. |
Examples
Dynamic DNS
If you have a Linux (or BSD) server behind a dynamic IP Address you can use the following entry in your crontab to update a DNS entry on my-webspace.at to always point to your server:
15 * * * * wget -O - 'https://4.panel.my-webspace.at/dns-update.php?key=Key to your A record&a=remote' > /dev/null 2>&1
If you have an IPv6 enabled connection you probably want to update IPv6 entries as well:
15 * * * * wget -O - 'https://6.panel.my-webspace.at/dns-update.php?key=Key to your AAAA record&aaaa=remote' > /dev/null 2>&1
Fetch IP address
This API can also be used to fetch the current IP Address. For example with jQuery:
jQuery.get("https://panel.my-webspace.at/dns", function(data) {
var your_ip = data["remote-ip"];
alert("Your IP is " + your_ip);
}, "JSON");
Using the API with Letsencrypt DNS Challenges
A DNS challenge is currently the only way to get wildcard certificates. The MyWebspace DNS API allows you to use this feature.
Step 1: Create a TXT record in the panel, named _acme-challenge.example.com, replace example.com with your actual domain or subdomain. Wildcards only work for one level, so the above entry will work for example.com, foo.example.com and bar.example.com, but not foo.bar.example.com. The data entry of the txt dns-record can be a random string. Note, the entries Autoupdate-key for the next step. This is the key, which you have to use in the 2nd step.
Step 2: Create a file /root/dns-hook.sh on the machine which will receive the certificate. Note that this does not have to be the server which will host the content, but most likely it is:
#!/bin/sh wget -O - "https://panel.my-webspace.at/dns?key=**key-here**&sync=true&txt=$CERTBOT_VALIDATION" >&2
Don't forget to make it executable: chmod +x /root/dns-hook.sh
Step 3: Run certbot, replace example.com with your actual domain. Remove the -d *.example.com part if you only want a regular certificate, not a wildcard certificate.
certbot certonly --manual --preferred-challenges dns -d 'example.com' -d '*.example.com' --agree-tos --manual-auth-hook /root/dns-hook.sh
Note: You can also use this if your domain is not hosted by MyWebspace, as long as you have at least one MyWebspace hosted domain. Let's assume example.com is at MyWebspace but example.org isn't. You want to create a Certificate for *.example.org. The way you can do this, is that you first create a TXT record in example.com, for example _org-validation.example.com. Use its Autoupdate key in the steps above. Then you create a CNAME record on your other provider. Call it _acme-challenge.example.org and have it point to this new TXT record _org-validation.example.com at MyWebspace. Take into consideration that your external provider may take a while to publish the CNAME, so verify it has before continuing with Step 2.