# SGX API Co-signer on-prem setup issues

**URL:** <https://community.fireblocks.com/t/sgx-api-co-signer-on-prem-setup-issues/2347>\
**Category:** Support\
**Created:** [April 2, 2025, 9:22pm UTC](https://community.fireblocks.com/t/sgx-api-co-signer-on-prem-setup-issues/2347 "2025-04-02T21:22:12Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mattboston](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@mattboston](https://community.fireblocks.com/u/mattboston)\
**Post date:** [April 2, 2025, 9:22pm UTC](https://community.fireblocks.com/t/sgx-api-co-signer-on-prem-setup-issues/2347/1 "2025-04-02T21:22:13Z")

</div>

I’m trying to setup the SGX API Co-signer on-prem. In Developer Center I created my api user (in testnet), then setup the co-signer and got the token. I then downloaded the shell script, set executable bit and ran “./cosigner setup” and entered the token. When I look at the logs, it has the following error. Both the user and co-signer say “Pending device setup”

```auto
customer_cosigner:20 INFO 02/04/2025 21:21:20,929 main.cpp(1013) ::main - Cosigner Version: 13 Commit Hash: 4ec196aec5 Context={}
customer_cosigner:20 FATAL 02/04/2025 21:21:20,929 main.cpp(1197) ::main - Cosigner not initialized Context={}

```

---

<div class="post-metadata">

**Author:** ![yoji](https://avatars.discourse-cdn.com/v4/letter/y/977dab/32.png) [@yoji](https://community.fireblocks.com/u/yoji)\
**Post date:** [April 2, 2025, 9:54pm UTC](https://community.fireblocks.com/t/sgx-api-co-signer-on-prem-setup-issues/2347/2 "2025-04-02T21:54:20Z")

</div>

Hi @mattboston – from the logs you shared, it looks like the cosigner client was never started after setup. Can you run: `./cosigner start` and let me know if the user finishes the device setup? Thanks!

---

<div class="post-metadata">

**Author:** ![mattboston](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@mattboston](https://community.fireblocks.com/u/mattboston)\
**Post date:** [April 2, 2025, 10:46pm UTC](https://community.fireblocks.com/t/sgx-api-co-signer-on-prem-setup-issues/2347/3 "2025-04-02T22:46:15Z")

</div>

I did run `./cosigner start`. But here’s the output from doing it again. I’ve also tried to stop, check `docker ps`, then start again.

```auto
root@fblx-tn-cs1:~/cosigner-new# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
351aac9bfd9b registry.gitlab.com/customer-cosigner/v2/cosigner:3.7.1 "/entrypoint.sh su f…" 2 hours ago Restarting (255) 1 second ago cosigner
root@fblx-tn-cs1:~/cosigner-new# ./cosigner start
Pulling cosigner docker
Running cosigner docker
root@fblx-tn-cs1:~/cosigner-new# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
351aac9bfd9b registry.gitlab.com/customer-cosigner/v2/cosigner:3.7.1 "/entrypoint.sh su f…" 2 hours ago Restarting (255) 5 seconds ago cosigner

```

---

<div class="post-metadata">

**Author:** ![mattboston](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@mattboston](https://community.fireblocks.com/u/mattboston)\
**Post date:** [April 3, 2025, 2:13pm UTC](https://community.fireblocks.com/t/sgx-api-co-signer-on-prem-setup-issues/2347/4 "2025-04-03T14:13:12Z")

</div>

Any other suggestions?

---

<div class="post-metadata">

**Author:** ![mattboston](https://avatars.discourse-cdn.com/v4/letter/m/ce7236/32.png) [@mattboston](https://community.fireblocks.com/u/mattboston)\
**Post date:** [April 3, 2025, 2:57pm UTC](https://community.fireblocks.com/t/sgx-api-co-signer-on-prem-setup-issues/2347/5 "2025-04-03T14:57:19Z")

</div>

Here’s my pre-requisite check based on the doc here ([Install SGX On-prem API Co-signer](https://developers.fireblocks.com/reference/install-api-cosigner-onprem))

```auto
root@fblx-tn-cs1:~# grep -m 1 'model name' /proc/cpuinfo
model name	: Intel(R) Xeon(R) Gold 6442Y

root@fblx-tn-cs1:~# grep -c ^processor /proc/cpuinfo
24

root@fblx-tn-cs1:~# cat /etc/os-release | grep -E "NAME|VERSION"
PRETTY_NAME="Ubuntu 22.04.5 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.5 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy

root@fblx-tn-cs1:~# uname -r
5.15.0-136-generic

root@fblx-tn-cs1:~# grep 'microcode' /proc/cpuinfo | uniq
microcode	: 0x2b000620

root@fblx-tn-cs1:~# echo "Total RAM: $(echo "scale=2; $(grep MemTotal /proc/meminfo | awk '{print $2}')/1024/1024" | bc)GB"
Total RAM: 117.67GB

root@fblx-tn-cs1:~# df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/md3 878G 7.2G 826G 1% /

root@fblx-tn-cs1:~# cpuid -1 | grep -i sgx
      SGX: Software Guard Extensions supported = true
      SGX_LC: SGX launch config supported = true
   Software Guard Extensions (SGX) capability (0x12/0):
      SGX1 supported = true
      SGX2 supported = true
      SGX ENCLV E*VIRTCHILD, ESETCONTEXT = false
      SGX ENCLS ETRACKC, ERDINFO, ELDBC, ELDUC = false
   SGX attributes: ECREATE SECS.ATTRIBUTES (0x12/1):
   SGX Enclave Page Cache (EPC) enumeration (0x12/0x2):
   SGX Enclave Page Cache (EPC) enumeration (0x12/0x3):
   SGX Enclave Page Cache (EPC) enumeration (0x12/0x4):

root@fblx-tn-cs1:~# grep -m 1 "^siblings" /proc/cpuinfo
siblings	: 24

root@fblx-tn-cs1:~# grep -m 1 "^cpu cores" /proc/cpuinfo
cpu cores	: 24

root@fblx-tn-cs1:~# dmidecode -t processor | grep -i speedstep

```

---

<div class="post-metadata">

**Author:** ![tenzin](https://avatars.discourse-cdn.com/v4/letter/t/c5a1d2/32.png) [@tenzin](https://community.fireblocks.com/u/tenzin)\
**Post date:** [September 8, 2025, 4:01am UTC](https://community.fireblocks.com/t/sgx-api-co-signer-on-prem-setup-issues/2347/6 "2025-09-08T04:01:53Z")

</div>

did you find the solution?