Incorrect Content-Type: must be textual to extract_string, JSON to extract_json. #99

kirillsurkov · 2023-07-01T16:00:19Z

Hi!
AltStore stopped working for me after updating to iOS 16.5.1
When I try to refresh the app I get this error:

AltServer.ServerError 2000
Incorrect Content-Type: must be textual to extract_string, JSON to extract_json.

The text was updated successfully, but these errors were encountered:

PinguThePenguin007 · 2023-07-01T21:55:50Z

Same error with iOS 16.1.1, so it most likely wasn't caused by updating D:
Also, any action (as in, downloading an app either through AltStore or AltServer, refreshing, retrieving appids, etc.) seems to prompt it.

wkddudwo · 2023-07-01T22:53:49Z

Same error. I guess you shouldn't update to 16.5.1 just yet.

boat1337 · 2023-07-02T11:19:55Z

Same error here, iOS 16.6 beta

WillDera · 2023-07-02T13:20:58Z

Same error. I guess you shouldn't update to 16.5.1 just yet.

Doesn't seem to be an iOS problem because @PinguThePenguin007 mentioned it not working on 16.1.1, I'm on 16.5 and I have the problem, and @boat1337 is on 16.6 beta.

PinguThePenguin007 · 2023-07-02T16:54:22Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux

Here's my guide to get it running again:

Download an alternative anisette-server from
https://github.com/Dadoum/Provision/releases/tag/2.1.0

Your architecture may differ, so i will refer to the executable as anisette-server

Extract it, mark it as executable
chmod +111 anisette-server
Run it like this:
./anisette-server -n 127.0.0.1 -p 6969
These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)
Open a new window/screen/etc.
Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969
Run AltServer, it should work! :DDD

WillDera · 2023-07-02T17:41:40Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux

Here's my guide to get it running again:

Download an alternative anisette-server from

https://github.com/Dadoum/Provision/releases/tag/2.1.0

Your architecture may differ, so i will refer to the executable as anisette-server

Extract it, mark it as executable

chmod +111 anisette-server

Run it like this:

./anisette-server -n 127.0.0.1 -p 6969

These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server

export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

Worked perfectly, Thank you!

LLuanZZ · 2023-07-02T18:17:25Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux

Here's my guide to get it running again:
1. Download an alternative anisette-server from
   https://github.com/Dadoum/Provision/releases/tag/2.1.0
Your architecture may differ, so i will refer to the executable as anisette-server
3. Extract it, mark it as executable
   chmod +111 anisette-server

4. Run it like this:
   ./anisette-server -n 127.0.0.1 -p 6969
   These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)

5. Open a new window/screen/etc.

6. Export the enviroment variable for AltServer so it connects to our server
   export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

7. Run AltServer, it should work! :DDD

1- Is it safe?

2- What do I put after -n and -p?
(Google translator)

boat1337 · 2023-07-02T19:21:46Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux

Here's my guide to get it running again:
1. Download an alternative anisette-server from
   https://github.com/Dadoum/Provision/releases/tag/2.1.0
Your architecture may differ, so i will refer to the executable as anisette-server
3. Extract it, mark it as executable
   chmod +111 anisette-server

4. Run it like this:
   ./anisette-server -n 127.0.0.1 -p 6969
   These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)

5. Open a new window/screen/etc.

6. Export the enviroment variable for AltServer so it connects to our server
   export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

7. Run AltServer, it should work! :DDD

can confirm, solved it by switching anisette servers

xeiAiex · 2023-07-02T19:57:09Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux

Here's my guide to get it running again:

Download an alternative anisette-server from
https://github.com/Dadoum/Provision/releases/tag/2.1.0

Your architecture may differ, so i will refer to the executable as anisette-server

Extract it, mark it as executable
chmod +111 anisette-server

Run it like this:
./anisette-server -n 127.0.0.1 -p 6969
These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

you're right; that does solve the problem. thank you!

LLuanZZ · 2023-07-02T19:59:18Z

you're right; that does solve the problem. thank you!

Did you put the same Hostname and Port? (Google translator)

xeiAiex · 2023-07-02T20:02:47Z

you need to use your own ip address. find it with something like ip addr or ifconfig. port 6969 worked for me.

PinguThePenguin007 · 2023-07-02T20:14:41Z

127.0.0.1 is localhost, so it should work fine :D

1- Is it safe?

about as safe as running AltServer-Linux in the first place, i think :D

2- What do I put after -n and -p?
(Google translator)

-n - your ip address / 127.0.0.1
-p - whatever port you like, just make sure it doesn't conflict with anything

LLuanZZ · 2023-07-02T20:52:29Z

127.0.0.1 is localhost, so it should work fine :D

1- Is it safe?

about as safe as running AltServer-Linux in the first place, i think :D

2- What do I put after -n and -p?
(Google translator)

-n - your ip address / 127.0.0.1 -p - whatever port you like, just make sure it doesn't conflict with anything

He crashed in this part, what do I do now?

WillDera · 2023-07-02T20:55:57Z

He crashed in this part, what do I do now?

Doesnt look like a crash, that's what is should show. Do the next step:

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

LLuanZZ · 2023-07-02T21:05:20Z

He crashed in this part, what do I do now?

Doesnt look like a crash, that's what is should show. Do the next step:

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

I didn't understand what to do in step 5 and 6

WillDera · 2023-07-03T00:30:15Z

He crashed in this part, what do I do now?

Doesnt look like a crash, that's what is should show. Do the next step:

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

I didn't understand what to do in step 5 and 6

In a new terminal window, run the command below:

export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Then start AltServer (however you used to) on your PC

Finally, connect your device to your PC as you usually do when refreshing/installing AltStore apps and go ahead with the refresh/install

LLuanZZ · 2023-07-03T14:10:41Z

He crashed in this part, what do I do now?

Doesnt look like a crash, that's what is should show. Do the next step:

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

I didn't understand what to do in step 5 and 6

In a new terminal window, run the command below:

export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Then start AltServer (however you used to) on your PC

Finally, connect your device to your PC as you usually do when refreshing/installing AltStore apps and go ahead with the refresh/install

It doesn't work.

kirillsurkov · 2023-07-03T15:26:33Z

@LLuanZZ try to run AltServer without sudo

LLuanZZ · 2023-07-03T17:01:16Z

now another error appears:

WillDera · 2023-07-03T17:36:44Z

now another error appears:

I'm not sure what this error means.
@PinguThePenguin007 care to look?

PinguThePenguin007 · 2023-07-03T22:48:45Z

He crashed in this part, what do I do now?

Doesnt look like a crash, that's what is should show. Do the next step:

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

I didn't understand what to do in step 5 and 6

In a new terminal window, run the command below:
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969
Then start AltServer (however you used to) on your PC
Finally, connect your device to your PC as you usually do when refreshing/installing AltStore apps and go ahead with the refresh/install

It doesn't work.

the port you specified in the anisette server and the port you enter before launching AltServer must not differ, you seemed to enter 6969 in anisette-server and 8659 in ALTSERVER_ANISETTE_SERVER

weird though, it shouldn't have fallen back to trying connecting to the default server, when i messed up earlier while trying to setup this, it just told me it couldn't connect to the address i specified and didn't do anything else...

maybe root access somehow affected it? i have no clue, but still, you should try entering the same port in both servers

LLuanZZ · 2023-07-04T01:02:16Z

He crashed in this part, what do I do now?

Doesnt look like a crash, that's what is should show. Do the next step:

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

I didn't understand what to do in step 5 and 6

In a new terminal window, run the command below:
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969
Then start AltServer (however you used to) on your PC
Finally, connect your device to your PC as you usually do when refreshing/installing AltStore apps and go ahead with the refresh/install

It doesn't work.

the port you specified in the anisette server and the port you enter before launching AltServer must not differ, you seemed to enter 6969 in anisette-server and 8659 in ALTSERVER_ANISETTE_SERVER

weird though, it shouldn't have fallen back to trying connecting to the default server, when i messed up earlier while trying to setup this, it just told me it couldn't connect to the address i specified and didn't do anything else...

maybe root access somehow affected it? i have no clue, but still, you should try entering the same port in both servers

It's on the same port.

I got my Apple ID emails mixed up, corrected it to the correct email, ran AltServer again and it showed this:

Alert: Could not install crunchyroll.ipa to unknown.
Unknown services response error. (-1)
Press any key to continue...
a
Error: com.rileytestut.AltServer.Localized (-1).
Finished!

wkddudwo · 2023-07-04T09:33:16Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux

Here's my guide to get it running again:

Download an alternative anisette-server from
https://github.com/Dadoum/Provision/releases/tag/2.1.0

Your architecture may differ, so i will refer to the executable as anisette-server

Extract it, mark it as executable
chmod +111 anisette-server

Run it like this:
./anisette-server -n 127.0.0.1 -p 6969
These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

First of all, thank you for your hard work. Unfortunately, I have a Raspberry Pi 4, but it doesn't work as smoothly as the anisette server works in Ubuntu. (aarch64, armv7)

Below is the error.

./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version GLIBC_2.33' not found (required by ./anisette-server-aarch64) ./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version GLIBC_2.32' not found (required by ./anisette-server-aarch64)
./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./anisette-server-aarch64)

I think it will be resolved in the near future, but it still doesn't work, so I hope it helps those who see this article.

Giuca002 · 2023-07-04T14:08:05Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux

Here's my guide to get it running again:
1. Download an alternative anisette-server from
   https://github.com/Dadoum/Provision/releases/tag/2.1.0
Your architecture may differ, so i will refer to the executable as anisette-server
3. Extract it, mark it as executable
   chmod +111 anisette-server

4. Run it like this:
   ./anisette-server -n 127.0.0.1 -p 6969
   These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)

5. Open a new window/screen/etc.

6. Export the enviroment variable for AltServer so it connects to our server
   export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

7. Run AltServer, it should work! :DDD

I have followed your guide and still get these errors...

Installing app...
Received response status code: 500
parse anisette data ret
Exception:Incorrect Content-Type: must be textual to extract_string, JSON to extract_json.
Alert: Installation Failed
    Incorrect Content-Type: must be textual to extract_string, JSON to extract_json.
Press any key to continue...

and I can confirm the alternative server is indeed running by going to http://127.0.0.1:6969 and seeing the json provided. And I also ran export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

LLuanZZ · 2023-07-04T21:39:15Z

@PinguThePenguin007
Any suggestions on how to solve my problem and @Giuca002 ?

Giuca002 · 2023-07-05T01:34:10Z

Nope im getting the same error here

BleakFox · 2023-07-05T11:36:01Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux

Here's my guide to get it running again:

Download an alternative anisette-server from
https://github.com/Dadoum/Provision/releases/tag/2.1.0

Your architecture may differ, so i will refer to the executable as anisette-server

Extract it, mark it as executable
chmod +111 anisette-server

Run it like this:
./anisette-server -n 127.0.0.1 -p 6969
These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

Didn't work for me.. same error

Curve · 2023-07-05T11:55:02Z

Does this error occur with the Windows version of altserver as well?

I looked at the commits a few days ago and it doesn't seem like the upstream repo was updated in any regards to this.

Does upstream use a different anisette server by default?

LLuanZZ · 2023-07-05T12:50:33Z

I don't think so, because in AltServer for Windows, the Anisette server is not used. The server is on your own PC (I think).

onyxcode · 2023-07-05T15:44:41Z

Can confirm this is an Anisette issue and not an iOS version issue, as I also had this problem on 15.6. Thanks for the fix!

PinguThePenguin007 · 2023-07-05T18:52:14Z

@PinguThePenguin007 Any suggestions on how to solve my problem and @Giuca002 ?

i'm really sorry, but i have no clue :(
i just tried random stuff and it worked
did you run as sudo? do you have any weird firewall configurations? i'm out of ideas D:

Giuca002 · 2023-07-05T21:08:40Z

Could be firewall related I will look into that

wkddudwo · 2023-07-06T02:15:08Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux
Here's my guide to get it running again:

Download an alternative anisette-server from
https://github.com/Dadoum/Provision/releases/tag/2.1.0

Your architecture may differ, so i will refer to the executable as anisette-server

Extract it, mark it as executable
chmod +111 anisette-server

Run it like this:
./anisette-server -n 127.0.0.1 -p 6969
These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

First of all, thank you for your hard work. Unfortunately, I have a Raspberry Pi 4, but it doesn't work as smoothly as the anisette server works in Ubuntu. (aarch64, armv7)

Below is the error.

./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version GLIBC_2.33' not found (required by ./anisette-server-aarch64) ./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version GLIBC_2.32' not found (required by ./anisette-server-aarch64) ./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./anisette-server-aarch64)

I think it will be resolved in the near future, but it still doesn't work, so I hope it helps those who see this article.

Problem solved by Dadoum.

The workaround is as follows.

If your glibc version is not correct, try the below.

apt update

apt upgrade

curl -fsS https://dlang.org/install.sh | bash -s ldc

git clone https://github.com/Dadoum/Provision --recursive

cd Provision

dub build -b release :anisette-server

The build has been completed. If you find the path as below, there will be provision_anisette_server.

cd bin/

chmod +x provision_anisette-server

./provision_anisette-server -n 127.0.0.1 -p 6969

It should now work correctly on Raspberry Pi.

SKProCH · 2023-07-07T12:12:34Z

If you don't want to install something to your PC, you can run ansiette server in docker:

docker run -d -v provision_config:/home/Chester/.config/Provision/ --restart=always -p 6969:6969 --name anisette dadoum/anisette-server:latest

And, follow the instructions:

Export the enviroment variable for AltServer so it connects to our server
```
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969/
```
Run AltServer, it should work! :DDD

han9over · 2023-07-07T20:23:08Z

I’m running anisette in docker and using 2 screens. One for netmuxd and another for altserver. I had to run netmuxd in sudo for Wi-Fi refresh to work. As I’m running netmuxd in sudo, I have to run altserver in sudo too. It’s fine because I can sudo first and do export of anisette url and then run altserver. Everything works fine but have a weird issue. Not sure if it’s related.

after some time, when I try to go do refresh of AltStore in the app, it says that it can’t use previous provisioning profile and asks to refresh the whole app, that basically invalidates old profiles and apps that I have. When I hit refresh it basically reinstalls the apps. It’s ok. Main challenge is with uyouplus as I have to uninstall and reinstall the app.

powenn · 2023-07-08T00:09:31Z

Try this
https://github.com/powenn/AltServer-Linux-PyScript

All you need is run the script and everything works for you

And if want you can use it as an app

han9over · 2023-07-08T12:02:51Z

If you don't want to install something to your PC, you can run ansiette server in docker:
docker run -d -v provision_config:/home/Chester/.config/Provision/ --restart=always -p 6969:6969 --name anisette dadoum/anisette-server:latest
And, follow the instructions:
Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969/
Run AltServer, it should work! :DDD

does the export work if you put that in profile.d making it system level so we can do sudo? I tried running netmuxd without sudo and it doesn't see my devices. so when I run netmuxd without sudo, I have to run altserver as sudo too.

hroy123 · 2023-07-09T14:51:27Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux
Here's my guide to get it running again:

Download an alternative anisette-server from
https://github.com/Dadoum/Provision/releases/tag/2.1.0

Your architecture may differ, so i will refer to the executable as anisette-server

Extract it, mark it as executable
chmod +111 anisette-server

Run it like this:
./anisette-server -n 127.0.0.1 -p 6969
These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

First of all, thank you for your hard work. Unfortunately, I have a Raspberry Pi 4, but it doesn't work as smoothly as the anisette server works in Ubuntu. (aarch64, armv7)
Below is the error.
./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version GLIBC_2.33' not found (required by ./anisette-server-aarch64) ./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version GLIBC_2.32' not found (required by ./anisette-server-aarch64) ./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./anisette-server-aarch64)
I think it will be resolved in the near future, but it still doesn't work, so I hope it helps those who see this article.

Problem solved by Dadoum.

The workaround is as follows.

If your glibc version is not correct, try the below.

apt update

apt upgrade

curl -fsS https://dlang.org/install.sh | bash -s ldc

git clone https://github.com/Dadoum/Provision --recursive

cd Provision

dub build -b release :anisette-server

The build has been completed. If you find the path as below, there will be provision_anisette_server.

cd bin/

chmod +x provision_anisette-server

./provision_anisette-server -n 127.0.0.1 -p 6969

It should now work correctly on Raspberry Pi.

Compiling anisette is not working on my orange pi zero 2 (armbian bullseye). Dud cannot be compiled on arch64. So I tried the cmake route described in Dadoum readme file but it’s not working either. The reason is that the D compiler (ldc2) is not working for compiling anisette. I know that the method described in all the posts above using anisette binary works well if I upgrade armbian to Bookworm version (glibc ver 36), but in that case I loose wifi because there no working wifi drivers for orange pi in Bookworm. Does anyone know of a D compiler working on aarch64?

han9over · 2023-07-09T14:53:45Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux
Here's my guide to get it running again:

Download an alternative anisette-server from
https://github.com/Dadoum/Provision/releases/tag/2.1.0

Your architecture may differ, so i will refer to the executable as anisette-server

Extract it, mark it as executable
chmod +111 anisette-server

Run it like this:
./anisette-server -n 127.0.0.1 -p 6969
These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

First of all, thank you for your hard work. Unfortunately, I have a Raspberry Pi 4, but it doesn't work as smoothly as the anisette server works in Ubuntu. (aarch64, armv7)
Below is the error.
./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version GLIBC_2.33' not found (required by ./anisette-server-aarch64) ./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version GLIBC_2.32' not found (required by ./anisette-server-aarch64) ./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./anisette-server-aarch64)
I think it will be resolved in the near future, but it still doesn't work, so I hope it helps those who see this article.

Problem solved by Dadoum.
The workaround is as follows.
If your glibc version is not correct, try the below.
apt update
apt upgrade
curl -fsS https://dlang.org/install.sh | bash -s ldc
git clone https://github.com/Dadoum/Provision --recursive
cd Provision
dub build -b release :anisette-server
The build has been completed. If you find the path as below, there will be provision_anisette_server.
cd bin/
chmod +x provision_anisette-server
./provision_anisette-server -n 127.0.0.1 -p 6969
It should now work correctly on Raspberry Pi.

Compiling anisette is not working on my orange pi zero 2 (armbian bullseye). Dud cannot be compiled on arch64. So I tried the cmake route described in Dadoum readme file but it’s not working either. The reason is that the D compiler (ldc2) is not working for compiling anisette. I know that the method described in all the posts above using anisette binary works well if I upgrade armbian to Bookworm version (glibc ver 36), but in that case I loose wifi because there no working wifi drivers for orange pi in Bookworm. Does anyone know of a D compiler working on aarch64?

Did you try using docker? I haven’t compiled it. I have a pi 4 and just running on docker works perfectly.

cyrilpower · 2023-07-10T09:04:36Z

It looks like root of the problem is not anisette. I tried to update anisette docker, but it did't help. I noticed, that altserver working properly when I running it from shell and giving this error when I start it like systemd unit. After some research I found that adding this line to altserver systemd unit:
Environment="ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969/"
make altserver work properly again.
OS: Ubuntu 20.04(armv7), Orange PI PC

hroy123 · 2023-07-10T14:25:18Z

Did you try using docker? I haven’t compiled it. I have a pi 4 and just running on docker works perfectly.

Thanks for the suggestion!
Unfortunately, Docker refuses to run properly on my Orange pi zero2 (Armbian_21.08.9_Orangepizero2_bullseye_legacy_kernel 4.9.255). I followed the Armbian doc and it installs okay, but the service refuses to load. I need to investigate that further...

han9over · 2023-07-10T16:40:12Z

Try this https://github.com/powenn/AltServer-Linux-PyScript

All you need is run the script and everything works for you

And if want you can use it as an app

Does this work on raspberry pi? Also did you fix the Wi-Fi refreshing?

powenn · 2023-07-11T00:59:58Z

Try this https://github.com/powenn/AltServer-Linux-PyScript

All you need is run the script and everything works for you

And if want you can use it as an app

Does this work on raspberry pi? Also did you fix the Wi-Fi refreshing?

WiFi refreshing fixed, pi should work

pinkeggy · 2023-07-11T18:39:32Z

If i run anisette-server with following command on my raspberry pi 2 model B with ubuntu running on it:
./anisette-server-armv7 -n 127.0.0.1 -p 6969
which i donwloaded from this link:
https://github.com/Dadoum/Provision/releases/tag/2.1.0

I'm getting this error:
./anisette-server-armv7 -n 127.0.0.1 -p 6969 app INFO 2023-07-11T20:37:24.462 anisette-server-provision v2.1.0 Segmentation fault (core dumped)

And if I try to build anisette-server on it with following command:

git clone https://github.com/Dadoum/Provision --recursive && cd Provision && mkdir build && cd build && cmake -G Ninja .. -DCMAKE_BUILD_TYPE=Release && ninja

I'm getting the following error:
-- The D compiler identification is unknown CMake Error at CMakeLists.txt:4 (project): No CMAKE_D_COMPILER could be found. Tell CMake where to find the compiler by setting either the environment variable "DC" or the CMake cache entry CMAKE_D_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. -- Configuring incomplete, errors occurred!

Can someone help me?

pinkeggy · 2023-07-11T19:14:07Z

If i run anisette-server with following command on my raspberry pi 2 model B with ubuntu running on it: ./anisette-server-armv7 -n 127.0.0.1 -p 6969 which i donwloaded from this link: https://github.com/Dadoum/Provision/releases/tag/2.1.0

I'm getting this error: ./anisette-server-armv7 -n 127.0.0.1 -p 6969 app INFO 2023-07-11T20:37:24.462 anisette-server-provision v2.1.0 Segmentation fault (core dumped)

And if I try to build anisette-server on it with following command:

git clone https://github.com/Dadoum/Provision --recursive && cd Provision && mkdir build && cd build && cmake -G Ninja .. -DCMAKE_BUILD_TYPE=Release && ninja

I'm getting the following error: -- The D compiler identification is unknown CMake Error at CMakeLists.txt:4 (project): No CMAKE_D_COMPILER could be found. Tell CMake where to find the compiler by setting either the environment variable "DC" or the CMake cache entry CMAKE_D_COMPILER to the full path to the compiler, or to the compiler name if it is in the PATH. -- Configuring incomplete, errors occurred!

Can someone help me?

i'm one step forward

with this command i was able to install D Compiler:
sudo apt-get install -y gdc

but then i got this error:
ninja: build stopped: subcommand failed. CMake Error at /usr/share/cmake-3.24/Modules/FetchContent.cmake:1604 (message): Build step for slf4d_proj failed: 1 Call Stack (most recent call first): /usr/share/cmake-3.24/Modules/FetchContent.cmake:1744:EVAL:2 (__FetchContent_directPopulate) /usr/share/cmake-3.24/Modules/FetchContent.cmake:1744 (cmake_language) /usr/share/cmake-3.24/Modules/FetchContent.cmake:1958 (FetchContent_Populate) cmake/cmake-d/cmake-d/UseDub.cmake:103 (FetchContent_MakeAvailable) cmake/dependencies.cmake:6 (DubProject_Add) CMakeLists.txt:10 (include) -- Configuring incomplete, errors occurred!

Has anyone an idea?

Staubgeborener · 2023-07-29T08:15:59Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux

Here's my guide to get it running again:
1. Download an alternative anisette-server from
   https://github.com/Dadoum/Provision/releases/tag/2.1.0
Your architecture may differ, so i will refer to the executable as anisette-server
3. Extract it, mark it as executable
   chmod +111 anisette-server

4. Run it like this:
   ./anisette-server -n 127.0.0.1 -p 6969
   These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)

5. Open a new window/screen/etc.

6. Export the enviroment variable for AltServer so it connects to our server
   export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

7. Run AltServer, it should work! :DDD

Works like a charm, saved my day!

MintyGitOut · 2023-12-28T23:34:31Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux

Here's my guide to get it running again:

Download an alternative anisette-server from
https://github.com/Dadoum/Provision/releases/tag/2.1.0

Your architecture may differ, so i will refer to the executable as anisette-server

Extract it, mark it as executable
chmod +111 anisette-server

Run it like this:
./anisette-server -n 127.0.0.1 -p 6969
These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

my man

TheCheddarCheese · 2024-01-05T14:11:08Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux

Here's my guide to get it running again:
1. Download an alternative anisette-server from
   https://github.com/Dadoum/Provision/releases/tag/2.1.0
Your architecture may differ, so i will refer to the executable as anisette-server
3. Extract it, mark it as executable
   chmod +111 anisette-server

4. Run it like this:
   ./anisette-server -n 127.0.0.1 -p 6969
   These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)

5. Open a new window/screen/etc.

6. Export the enviroment variable for AltServer so it connects to our server
   export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

7. Run AltServer, it should work! :DDD

it works through cable but not wifi, it says altserver could not find the device
(the pyscript version adds it fine though. not sure what's up with that.)

Spiksee3 · 2024-01-18T09:26:01Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux
Here's my guide to get it running again:

Download an alternative anisette-server from
https://github.com/Dadoum/Provision/releases/tag/2.1.0

Your architecture may differ, so i will refer to the executable as anisette-server

Extract it, mark it as executable
chmod +111 anisette-server

Run it like this:
./anisette-server -n 127.0.0.1 -p 6969
These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

First of all, thank you for your hard work. Unfortunately, I have a Raspberry Pi 4, but it doesn't work as smoothly as the anisette server works in Ubuntu. (aarch64, armv7)
Below is the error.
./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version GLIBC_2.33' not found (required by ./anisette-server-aarch64) ./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version GLIBC_2.32' not found (required by ./anisette-server-aarch64) ./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./anisette-server-aarch64)
I think it will be resolved in the near future, but it still doesn't work, so I hope it helps those who see this article.

Problem solved by Dadoum.

The workaround is as follows.

If your glibc version is not correct, try the below.

apt update

apt upgrade

curl -fsS https://dlang.org/install.sh | bash -s ldc

git clone https://github.com/Dadoum/Provision --recursive

cd Provision

dub build -b release :anisette-server

The build has been completed. If you find the path as below, there will be provision_anisette_server.

cd bin/

chmod +x provision_anisette-server

./provision_anisette-server -n 127.0.0.1 -p 6969

It should now work correctly on Raspberry Pi.

when i try this i get up to dub build and then get a semver error

Spikesee3@Spikesee3pi:~/Altstore-Stuff/Provision $ dub build -b release :anisette-server Invalid SemVer format: 30d152e88767611e10048b25777ecb5f9075f87c

CrCrate · 2024-02-08T16:13:05Z

I have found the source of the issue, it seems that the default anisette-server has changed something and broke AltServer-Linux
Here's my guide to get it running again:

Download an alternative anisette-server from
https://github.com/Dadoum/Provision/releases/tag/2.1.0

Your architecture may differ, so i will refer to the executable as anisette-server

Extract it, mark it as executable
chmod +111 anisette-server

Run it like this:
./anisette-server -n 127.0.0.1 -p 6969
These are my hostname (argument -n) and port (-p) of choice, you may pick something else :)

Open a new window/screen/etc.

Export the enviroment variable for AltServer so it connects to our server
export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

Run AltServer, it should work! :DDD

First of all, thank you for your hard work. Unfortunately, I have a Raspberry Pi 4, but it doesn't work as smoothly as the anisette server works in Ubuntu. (aarch64, armv7)
Below is the error.
./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version GLIBC_2.33' not found (required by ./anisette-server-aarch64) ./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version GLIBC_2.32' not found (required by ./anisette-server-aarch64) ./anisette-server-aarch64: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./anisette-server-aarch64)
I think it will be resolved in the near future, but it still doesn't work, so I hope it helps those who see this article.

Problem solved by Dadoum.

The workaround is as follows.

If your glibc version is not correct, try the below.

apt update

apt upgrade

curl -fsS https://dlang.org/install.sh | bash -s ldc

git clone https://github.com/Dadoum/Provision --recursive

cd Provision

dub build -b release :anisette-server

The build has been completed. If you find the path as below, there will be provision_anisette_server.

cd bin/

chmod +x provision_anisette-server

./provision_anisette-server -n 127.0.0.1 -p 6969

It should now work correctly on Raspberry Pi.

for anyone trying this on a low memory pi (<=1GB?), use the --build-mode=singleFile build argument, and if thats not enough also the lowmem build option in dub.sdl

PinguThePenguin007 mentioned this issue Jul 2, 2023

Error #100

Open

ACTrooper mentioned this issue Jul 4, 2023

Unable To Bind Websocket Dadoum/Provision#82

Closed

powenn mentioned this issue Jul 5, 2023

Incorrect Content-Type: must be textual to extract_string, JSON to extract_json. powenn/AltServer-Linux-ShellScript#59

Closed

Johnny008 mentioned this issue Feb 9, 2025

Failed to connect to any resolved endpoint. powenn/AltServer-Linux-PyScript#49

Open

Incorrect Content-Type: must be textual to extract_string, JSON to extract_json. #99

Incorrect Content-Type: must be textual to extract_string, JSON to extract_json. #99

Comments

kirillsurkov commented Jul 1, 2023 • edited Loading

PinguThePenguin007 commented Jul 1, 2023

wkddudwo commented Jul 1, 2023

boat1337 commented Jul 2, 2023

WillDera commented Jul 2, 2023

PinguThePenguin007 commented Jul 2, 2023 • edited Loading

WillDera commented Jul 2, 2023 • edited Loading

LLuanZZ commented Jul 2, 2023

boat1337 commented Jul 2, 2023

xeiAiex commented Jul 2, 2023

LLuanZZ commented Jul 2, 2023

xeiAiex commented Jul 2, 2023 • edited Loading

PinguThePenguin007 commented Jul 2, 2023 • edited Loading

LLuanZZ commented Jul 2, 2023

WillDera commented Jul 2, 2023 • edited Loading

LLuanZZ commented Jul 2, 2023

WillDera commented Jul 3, 2023 • edited Loading

LLuanZZ commented Jul 3, 2023

kirillsurkov commented Jul 3, 2023

LLuanZZ commented Jul 3, 2023

WillDera commented Jul 3, 2023

PinguThePenguin007 commented Jul 3, 2023 • edited Loading

LLuanZZ commented Jul 4, 2023

wkddudwo commented Jul 4, 2023

Giuca002 commented Jul 4, 2023

LLuanZZ commented Jul 4, 2023

Giuca002 commented Jul 5, 2023

BleakFox commented Jul 5, 2023

Curve commented Jul 5, 2023

LLuanZZ commented Jul 5, 2023

onyxcode commented Jul 5, 2023 • edited Loading

PinguThePenguin007 commented Jul 5, 2023

Giuca002 commented Jul 5, 2023

wkddudwo commented Jul 6, 2023 • edited Loading

SKProCH commented Jul 7, 2023

han9over commented Jul 7, 2023 • edited Loading

powenn commented Jul 8, 2023 • edited Loading

han9over commented Jul 8, 2023

hroy123 commented Jul 9, 2023

han9over commented Jul 9, 2023

cyrilpower commented Jul 10, 2023 • edited Loading

hroy123 commented Jul 10, 2023 • edited Loading

han9over commented Jul 10, 2023

powenn commented Jul 11, 2023

pinkeggy commented Jul 11, 2023

pinkeggy commented Jul 11, 2023

Staubgeborener commented Jul 29, 2023

MintyGitOut commented Dec 28, 2023

TheCheddarCheese commented Jan 5, 2024 • edited Loading

Spiksee3 commented Jan 18, 2024

CrCrate commented Feb 8, 2024

kirillsurkov commented Jul 1, 2023 •

edited

Loading

PinguThePenguin007 commented Jul 2, 2023 •

edited

Loading

WillDera commented Jul 2, 2023 •

edited

Loading

xeiAiex commented Jul 2, 2023 •

edited

Loading

PinguThePenguin007 commented Jul 2, 2023 •

edited

Loading

WillDera commented Jul 2, 2023 •

edited

Loading

WillDera commented Jul 3, 2023 •

edited

Loading

PinguThePenguin007 commented Jul 3, 2023 •

edited

Loading

onyxcode commented Jul 5, 2023 •

edited

Loading

wkddudwo commented Jul 6, 2023 •

edited

Loading

han9over commented Jul 7, 2023 •

edited

Loading

powenn commented Jul 8, 2023 •

edited

Loading

cyrilpower commented Jul 10, 2023 •

edited

Loading

hroy123 commented Jul 10, 2023 •

edited

Loading

TheCheddarCheese commented Jan 5, 2024 •

edited

Loading