One week is FREE to test Hosting Mate


I'm here for the first time. How can I be sure you can trully provide the service?
We provide 7 days free hosting period for all clients. You can test us out during this period to be sure we provide good and stable onion hosting.
What payment ways are available?
We accept Bitcoin, Litecoin, Dash, Dogecoin, Ethereum, Monero and Tether as a payment way.
Can I pay by other crypto?
Yes, just contact us on [email protected]
Can I pay by Paypal or credit card?
No, you can't, because of security.
Can I host a porn site?
Yes as long as your content is legal you may upload adult content.
I just uploaded my page, but it's broken. HELP!
Most likely your site makes use of rewriting rules, which are typically located in an .htaccess file or are mentioned in a README file. Just contact us on [email protected] in this case.
I have an .htaccess file, but it doesn't work. How can I fix it?
.htaccess files are meant for Apache2 webservers. My server is based on NginX, which is much faster due to using static configuration files and not reading files like .htaccess at runtime. You can contact us on [email protected] and tell your sites address where the .htaccess file is. We will then check your .htaccess and convert the rules to NginX rules and apply those.
What is the directory structure for when I connect via sftp?
There are several directories you on the server for your account:
Maildir - used to store your mails in (don't touch it)
data - You can store application data here that should not be accessible via your site. E.g. configuration or database files.
tmp - anything saved here will automatically be deleted after about 24 hours
www - this is where you upload your website which becomes then available under your domain.
logs - you will find webserver logs here.
ssh - by uploading your ssh public key as authorzed_keys in this folder, you can authenticate to sftp using your ssh key, without a password
I'm using CloudFlare, but when I open my site, it shows too many redirects.
By default CloudFlare makes unencrypted requests to the backend server, but our server tells any client that wants an insecure connection to upgrade to a secure connection and use https:// instead of http://. CloudFlare just forwards this redirection to the client, which then again asks CloudFlare for the same thing again, but CloudFlare still connects to our server via an insecure http:// connection. To fix this, go to your CloudFlare dashboard and manage your domains settings. Under "Crypto" you can find settings for SSL. Change the setting from Flexible to Full, which makes CloudFlare use a secure https:// connection when talking to our server.