Frequently Asked Questions

This page contains some common questions and answers.

For more help resources, check all Support Options.

Active user vs login prohibited user

In DevOps Control, an active user refers to a user that has activated their account via email.

A login prohibited user is a user that is not allowed to log in to DevOps Control anymore.

What is Swagger?

Swagger is what DevOps Control uses for its API documentation.

All DevOps Control instances have the built-in API and there is no way to disable it completely. For more information, refer to API docs of DevOps Control.

Adjusting your server for public/private use

Restricted users

Restricted users are limited to a subset of the content based on their organization/team memberships and collaborations, ignoring the public flag on organizations/repos etc.

Example use case: A company runs a DevOps Control instance that requires login. Most repos are public (accessible/browsable by all co-workers).

At some point, a customer or third party needs access to a specific repo and only that repo. Making such a customer account restricted and granting any needed access using team membership(s) and/or collaboration(s) is a simple way to achieve that without the need to make everything private.

DevOps Control is running slow

The most common cause of this issue is the loading of federated avatars.

To turn off the avatars, follow these steps:

  1. Log in to DevOps Control as an Administrator.

  2. Go to Configuration > Settings.

  3. In the Picture and Avatar section, turn on Disable Gravatar and turn off Enable Federated Avatars.

  4. Click Save to apply changes.

Push Hook/Webhook

If you can push but cannot see push activities on the home dashboard, or the push does not trigger webhook, it is likely that the git hooks are not working.

There is a possibility that the git hooks are out of sync, run the following command on the site admin panel:

Resynchronize pre-receive, update and post-receive hooks of all repositories

SSH issues

If you cannot reach repositories over ssh, but https works fine, consider looking into the following.

SSH Common Errors

Permission denied (publickey).
fatal: Could not read from remote repository.

This error signifies that the server rejected a log in attempt, check the following things:

  • On the client:
    • Ensure the public and private ssh keys are added to the correct DevOps Control user.
    • Make sure there are no issues in the remote url. In particular, ensure the name of the Git user (before the @) is spelled correctly.
    • Ensure public and private ssh keys are correct on client machine.

LFS Issues

For issues concerning LFS data upload

batch response: Authentication required: Authorization error: <GITEA_LFS_URL>/info/lfs/objects/batch
Check that you have proper access to the repository
error: failed to push some refs to '<GIT_REPO_URL>'

By default, your LFS token will expire after 1 day. If you have a slow connection or a large file (or both), it might finish uploading within the time limit.

Why is my markdown broken

In DevOps Control, we use goldmark for markdown rendering, which is CommonMark compliant.

If you have markdown that worked as you expected and after upgrading, it is not working anymore, look through the CommonMark spec to see whether the problem is due to a bug or non-compliant syntax.

If it is the latter, usually there is a compliant alternative listed in the spec.

Why are Emoji displaying only as placeholders or in monochrome

DevOps Control requires the system or browser to have one of the supported Emoji fonts installed, which are Apple Color Emoji, Segoe UI Emoji, Segoe UI Symbol, Noto Color Emoji and Twemoji Mozilla. Generally, the operating system should already provide one of these fonts, but especially on Linux, it might be necessary to install them manually.