> For the complete documentation index, see [llms.txt](https://docs.specsolutions.eu/specsync/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.specsolutions.eu/specsync/jira/contact/troubleshooting.md).

# Troubleshooting

This page contains common issues and their solution. To better understand the synchronization process that led to the error, you can try to re-run the synchronization with an additional `--verbose` option.

If you don't find your issues here, please [contact support](/specsync/jira/contact/specsync-support.md).

### Unable to find or restore package error when installing or restoring SpecSync as a .NET tool <a href="#nuget-package-not-found" id="nuget-package-not-found"></a>

When you install SpecSync as a [.NET tool](/specsync/jira/installation/dotnet-core-tool.md), you might receive errors during the `dotnet tool install SpecSync.Jira` or the `dotnet tool restore` commands. The error message might contain `Unable to find package SpecSync.Jira` or `The tool package could not be restored`.

The problem is usually that there is a custom NuGet source configured in your organization that does not mirror SpecSync packages.

**Solution 1:** For the installation you can specify the official NuGet source by adding the `--add-source https://api.nuget.org/v3/index.json --ignore-failed-sources` options to the install or restore command.

E.g. the installation with specified NuGet source would be...

```bash
dotnet tool install SpecSync.Jira --add-source  https://api.nuget.org/v3/index.json --ignore-failed-sources
```

**Solution 2:** You can change your local NuGet configuration or the `NuGet.config` file of your project to include the official NuGet source `https://api.nuget.org/v3/index.json`. Alternatively you can ask the administrator of your custom NuGet source to mirror the SpecSync NuGet packages.

### No usable version of libssl was found error when running SpecSync Linux binaries on Ubuntu 22.04 <a href="#no-usable-libssl-ubuntu2204" id="no-usable-libssl-ubuntu2204"></a>

When the Linux binary package of an older SpecSync version is executed on Ubuntu 22.04 the synchronization might fail with the error message `No usable version of libssl was found`.

This is caused by the SSL library incompatibility between .NET Core 3.1 and Ubuntu 22.04.

**Solution 1:** You can use the Ubuntu 20.04 stable version for these SpecSync versions where you can have compatible SSL packages (`libssl1.1`).

**Solution 2:** Upgrade SpecSync for Jira to v1.1.1. Those versions use .NET 6 for the Linux binaries that are compatible with `libssl3` available for Ubuntu 22.04.

**Solution 3:** The compatibility can also be achieved by downgrading and installing the necessary libssl library. This can be achieved by adding the following command to your `Dockerfile` (source: [StackOverflow post](https://stackoverflow.com/a/72137153/26530)):

```
RUN wget http://archive.ubuntu.com/ubuntu/pool/main/o/openssl1.0/libssl1.0.0_1.0.2n-1ubuntu5_amd64.deb \
    && dpkg -i libssl1.0.0_1.0.2n-1ubuntu5_amd64.deb
```

### 'W5113: Unable to find attachment file' warnings when publishing results from TRX file <a href="#issue1668" id="issue1668"></a>

When the TRX logger is used with `dotnet test` command for running the tests to be published with SpecSync, you might encounter warnings like

* `W5113: Unable to find attachment file '<some-attachment-path>'. Ignored.`

The issue is probably caused by the TRX logger, that saves the attachment files to the test output folder (usually the `TestResults` folder of the project), but the TRX file is saved elsewhere, for example because a folder is specified for the TRX logger in the `LogFileName` setting, like `--logger "trx;LogFileName=..\results.trx`.

**Solution:** Use the `--results-directory` setting of `dotnet test` to specify the results directory, and use the `LogFileName` only to specify the file name. E.g. `dotnet test --logger trx;logfilename=results.trx --results-directory "C:\MyProject"`.