So I’ve been running into problems with part of the code provided in the Datum instructions for setting up single proxy.
I’m trying to solo mine and I was able to set up my Bitaxe entering the IP of my start 9 and well as the correct port 2334. When I look in the Datum gateway status page the right side of the status page shows my Bitaxe is online but the right side of the page shows 0 connections.
I think this might be a result of incompletion of the process for setting up Singe Proxy.
I’m specifically running into problems with the part of the long string of code that begins with echo -e. When I copy paste and enter it into my command prompt I either get a weird message that no such file or directory can be found and the root@start9 prompt doesn’t return and I just get an >
Can anyone help me to figure out what’s going on? I provided some photos to show what I see after entering each line of code up until the echo -e part of the code
I’m not seeing anything obviously wrong, but it’s tricky to follow screenshots that are a frozen moment in time.
For the service to be masked means there’s something wrong with it. You could run…
cat /lib/systemd/system/simpleproxy.datum.service
…to take a look inside. If it’s malformed or empty, that might explain things, and we can probably do a couple of things to get back on track. If it looks complete fine, then I’m not really sure what has happened.
What I do know, is that you can get into a starting position again with a simple reflash of the OS, if you needed to.
I re-flashed about 3 or different times and keep running into the same problem. For example yesterday after reflashing I attempted to ssh back into my server and received a message that the .local couldn’t be found. I had to use a Keygen command to fix it. And then when I enter the chroot command and hit enter ail I get are a bunch of values that just scroll all the way up the screen.
start9@extreme-thesis:~$ cat/lib/systemd/system/simpleproxy.datum.service
-bash: cat/lib/systemd/system/simpleproxy.datum.service: No such file or directory
root@extreme-thesis:~# /usr/lib/startos/scripts/chroot-and-upgrade
Syncing…
4,246,452,227 99% 432.01MB/s 0:00:09 (xfr#53523, to-chk=0/65630)
root@extreme-thesis:/# apt install simpleproxy -y
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following NEW packages will be installed:
simpleproxy
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 19.2 kB of archives.
After this operation, 57.3 kB of additional disk space will be used.
Get:1 Index of /debian bookworm/main amd64 simpleproxy amd64 3.5-1+b2 [19.2 kB]
Fetched 19.2 kB in 0s (280 kB/s)
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
Selecting previously unselected package simpleproxy.
(Reading database … 57615 files and directories currently installed.)
Preparing to unpack …/simpleproxy_3.5-1+b2_amd64.deb …
Unpacking simpleproxy (3.5-1+b2) …
Setting up simpleproxy (3.5-1+b2) …
Processing triggers for man-db (2.11.2-2) …
[Service]
Type=simple
Restart=always
RestartSec=3
nExecStartPre=/bin/bash -c “/bin/systemctl set-environment IP=$(ip route | grep default | awk {print
bash: }”)"\nExecStart=/usr/bin/simpleproxy -L ${IP}:23334-R datum.embassy:23335\n\n[Install]\nWantedBy=multi-
user.target: No such file or directory
root@extreme-thesis:/# systemctl enable simpleproxy.datum. service
Failed to enable unit, unit simpleproxy.datum…service does not exist.
So it looks like singproxy is being installed but something somewhere is going wrong. I copied and pasted the exact code from the Datum instructions. Could there be something wrong with part of the code somwehere?
