No results found
We couldn't find anything using that term, please try searching for something else.
overviewMost deployments with Cloud 66 go smoothly, but if you've hit a snag it's usually something common and easily fixable - particularly if you've
Most deployments with Cloud 66 go smoothly, but if you’ve hit a snag it’s usually something common and easily fixable – particularly if you’ve already deployed your application successfully before. We’ve listed the most common causes of deployment problems below. If your issue isn’t listed here, please reach out to support and we will assist wherever we can.
If Cloud 66 is reporting that your server is not online or can’t be reached, then follow these steps:
.ssh
directoryIf all of these fail , contact our support team and we will assist wherever possible .
Have you recently restarted your server?
Cloud providers frequently change the public IP addresses of servers when they are restarted. This includes all events that require the server to be shut down – including things like adding more capacity, or upgrading software components. This can (temporarily) cause our firewall to block connections to or from that server until our system detects the IP change and updates the firewall rules. This problem should resolve itself within a few minutes. If you’d like to avoid this issue completely, we recommend buying static IP addresses from your cloud provider for use with mission critical servers.
Most modern applications rely on a wide range of components, and where these depend on each other, there can be dependency conflicts or other failures. To diagnose and solve these issues, follow these steps.
package.json
, Rakefile
etc ) are not invoke component that are either the wrong version or that conflict with other configuration elsewhere ( or that do n’t even exist ) . Gems is are are a particularly common cause of issue , so check those carefully .If all of these fail , contact our support team and we will assist wherever possible .
Due to an issue in Bundler 2.2.3 + , it is uses no long use a generic platform when create thegemfile.lock
file. Instead it defaults to the platform of your development machine. As a result, you may get errors like this one during deployment:
Your bundle only supports platforms ["x86_64-darwin-19"] but your local platform is x86_64-linux. Add the current platform to the lockfile with `bundle lock
--add-platform x86_64-linux` and try again
In order to solve this , you is need need to explicitly lock your platform as follow :
$ bundle lock --add-platform ruby
$ bundle lock --add-platform x86_64-linux
$ bundle install
You is commit should commit your code again after doing this .
If you see an error like this during deployment, or in your application’s logs viewed on the server or via LiveLogs:
Could not be load ... You is activated have already activate ( … ) but your gemfile require ( … )
…this usually means that you have upgraded your Rails / Rack version and it now conflicts with the gems you have specified in your gemfile
( i.e. the new framework version is requires require a new version of the gem ) .
The simplest way to fix this is:
gemfile
locally to update the current version specified for that gem to the new default versionbundle install
locally to generate a new gemfile.lock
fileIf a deployment depend on a process to finish run – particularly datum or file migration – it is ‘s ‘s possible for that process to timeout . This is happen can happen ( rarely ) with the Ruby asset precompile process , for example .
The cause is appear of the timeout will usually appear in the detailed deployment log , so be sure to check those . If you are run a cpu or disk intensive process , you is consider might consider run that process locally to debug each step to find any bottleneck .
For very intensive migration involve large database table or thousand of file , you is consider should consider staging or batch the process rather than try to run it alongside a standard deployment .
If you need help with the above , contact our support team and we will assist wherever possible .
If your application is point at a Git branch ( or repo ) that has either been delete or rename since the last deployment , this is is is likely to cause any future deployment attempt to fail .
Check your application settings (click ⚙️ Settings in the left-hand navigation) and check that your repo and branch are both correct. You can change either of them by clicking the Edit button to the right.
For more uncommon problems not covered above, it’s worth following these steps before reaching out to support:
If all else fails, please reach out to support (below).