Skip to main content

Troubleshooting & FAQ for Appcircle Runner

Appcircle Runner FAQ​

We are facing a self-signed certificate error on builds.​

The certificate of your organization should be trusted on the Appcircle runner virtual machines.

You should refer to the Custom Certificates page for more details.

We are facing an "SSL certificate is not valid yet" error on builds.​

The runner VMs cannot connect to the servers to update their date and time due to network restrictions.

You should configure NTP server settings in the runner VMs. For updating base runners, please refer to the Update Base Images section.

For details on configuring NTP settings, you can refer to the NTP Configuration section and follow the steps.

We are facing a "connection timeout" / "connection reset" / "403 forbidden" error on builds.​

Especially if you're using external sources as dependencies that require access to certain URLs, you may encounter connection issues due to network restrictions.

To verify whether your Appcircle runner can access the URL, you can run the command below and check the output. Make sure to replace the example RubyGems URL below with the URL you faced network problems with while running the build.

curl -v https://rubygems.org

If you receive an "operation timed out", "connection timeout", "connection reset", or "403 forbidden" error, it indicates that the Appcircle runner is unable to access the URL due to network restrictions. In that case, you'll need to allow Appcircle runners to access the URL.

You can find the list of commonly required URLs for Appcircle runners here. Please note that the specific URL the Appcircle runner is unable to access may not be included in this list.

We can't register Appcircle runner to the server.​

First, you should check if your Appcircle runner can access the Appcircle server. You can run the command below to test this. You should change the example Appcircle URL for yourself.

curl -v https://api.appcircle.spacetech.com

You should check if there is a self-signed certificate problem. You can refer to the Custom Certificates page to trust the root CA certificate of your organization.

If you already trusted the root CA cert, you should check the Appcircle server's certificate. If it is too long, like 5 years, it should be trusted using the graphical user interface. You should open the Keychain Access application from the GUI and add the Appcircle server's certificate. After that, you should click on the certificate and select "Always trust".

We are facing "LoginName too long" error while running the screen command.​

The screen command has a bug with long usernames which has been fixed in the new versions.

If you are facing this error while trying to run Appcircle runner VMs on a macOS host, you should update the screen tool on the host machine with brew.

You should follow the steps below to update the screen tool:

  • Check the current version before updating.
screen --version
  • Install the up-to-date version using Homebrew.
brew install screen
  • Open a new terminal session to use the new screen.
caution

If you don't open a new terminal session, you cannot use the up-to-date screen since the current shell session has access to the older version.

  • Re-check the version to see if the update was done successfully.
screen --version