It's not working!¶
That's a very vague error description. Please exactly define what "it" is! In general, please make sure to have read and followed our help articles here and especially the install guides section. Step by step instructions to successfully deploy your application are included. You can also search for your topic of interest.
I can not connect via SFTP or SSH!¶
This can have multiple causes. Please make sure to grab the correct access credentials from the Dashboard for your App. See our SFTP article for more on that. We offer two access methods: SSH key and password. See our SSH key troubleshooting guide when using the later. Please also mind that SFTP and SSH login is only by Universal Apps. Professional Apps have remote SSH execution, see here.
I can not push code by Git!¶
Please also the question above on authentication. Check if SSH/SFTP is working for you and if Git is setup correctly. Also see our getting started with Git article, when you are new to this. Check out the Git troubleshooting section.
Composer update is failing!¶
That's likely because you have tried to run the Composer update on the App itself? That's not the way it is supposed to work for most workflows. Please also see the Composer article and especially the section on using Composer via SSH.
Old files are not deleted!¶
When deploying with Git, you might wonder why some old files have not been deleted from the Apps web storage, although you have deleted them from Git. That's not a bug, it's a feature. The Universal Stack has a persistent web storage, therefore the App can change the file system, like when uploading images. The Git repo and the web storage are not the same thing, so those changes will not be reflected in the Git repo. That's, why with the Universal Apps, the Git deployment uses an overwrite but not delete strategy. Changes will be applied, nothing will get deleted. You can login to that App by SSH or SFTP and delete the files manually. See more details in our deployment article.
I see a 403 error¶
I see a 404 error¶
That can have multiple causes: Maybe no code deployed, maybe wrong root path, maybe something else. Please see here.
My domain is not working!¶
That can have multiple causes. See the DNS and domain troubleshooting help, also make sure to read the info above.
I see an SSL cert error¶
Most likely you have just added your domain and it still takes a while until the Let's Encrypt certs will kick in. See our HTTPS troubleshooting section for more.
I see a 500 or a 503 error¶
You can likely find out about that yourself. Please see the App troubleshooting section for more.
I see a 504 error¶
504 errors are always time-outs. Something blocking or taking too long to process and the server times out.
This can be external API calls, database queries or image transforms (ImageMagick). Sometimes its plugins for CMS systems. 504 errors are usually connected to your code or the code you are using, not to general "server issues" here. It’s not likely that you can find something in the PHP error logs, as it just runs out of time.
Here are some tips to proceed:
- What is the request process with your page?
- Are you doing image transformations? How? Can you cache them?
- Are you making calls to external APIs?
- Is your page generating an expensive database query?
- Is there maybe some sort of loop you are creating in your code?
- Use a profiler like Blackfire or NewRelic to find the bottleneck!
- You can also decrease/increase max_timeout setting for debugging.
I uploaded Craft by SFTP but it's not working!¶
I clicked on my desired software but it got not installed!¶
The password reset is not working¶
Maybe you have used a different e-mail? Check if that is the correct e-mail. Or maybe you have setup 2FA earlier? Then you need to 1st just enter something with e-mail / password and then click on the "looking for 2FA" link. That's a design flaw on our side. Sorry.
It's still not working!¶
See what the error says and try to find out the solution yourself. This is a hosting platform for developers. We expect you to be able to help yourself. We just like to help you finding a solution yourself.
But I still have problems¶
Do not hesitate to contact us. Make sure to provide all details upfront so that we can back on you easily. See here on how to get good support quickly.
We are actively filtering deployment traffic for security reasons: too many falsy login attempts or parallel connections are considered dangerous and will therefore get blacklisted. This applies to all kind of deployment connections, S3, SSH/SFTP and Git.
Before thinking about blacklisting, please assure that it has worked before. We haven't had any support case where blacklisting occurred before it worked at least once. So, when you have not been able to connect before, chances are very very high that this is NOT blacklisting. Please see our access methods troubleshooting section next instead.
Get a new IP by disconnecting from the internet shortly, by restarting your router device. Ask us to remove your IP from the blacklisting ban.