Replies: 10 comments 11 replies
-
|
Just realised, that I am now completely locked out. I have no idea how to revert the Autosetting in the Jamulus Config file. |
Beta Was this translation helpful? Give feedback.
-
|
Oh, sorry for the post. Looks like I fixed it. I had to rerun the urlrelay.com/go command and now the VNC is possible again. For whatever reason, the IP did change. :( |
Beta Was this translation helpful? Give feedback.
-
|
@ChorusJam I'm glad you got it working. The raspberry pi will send its access URL with IP address to urlrelay.com on each boot. So, even if IP address changes, you should still be able to access via urlrelay.com/go. The /boot/payload/ directory only exists after burning the microSD card, but before first boot. Any files there will be copied to the root partition on first boot, then the /boot/payload/ directory is deleted. A few files are seeded there for possible editing if you want to make changes without booting. But you could place any file there and it will be copied. If you're burning multiple SD cards, it's very handy to be able to customize without booting. One use is to give each card a different NODE_ID by editing /boot/payload/etc/urlrelay/urlrelay.conf. Another is to set up autostart for jamulus or other jamming app. On my system, after burning a micro SD card using balenaEtcher, I need to unplug/re-plug my microSD-to-USB adapter in order to see the /boot partition. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Kevin, thanks for the background Info. The part "The /boot/payload/ directory only exists after burning the microSD card, but before first boot. " might be worth adding to the tutorial. |
Beta Was this translation helpful? Give feedback.
-
|
Hey, Kevin!
Do you ever have problems burning to new SD cards using Balena etcher? I
have been doing fine, but the last two SD cards in a run of about 10 didn't
boot up on the jamboxes. Went to re-etch them, and suddenly started
getting errors. Failed etching, can't read card, not enough storage space
on the card, etc. Tried on my mac and PC.
Thanks in advance,
*Matthew Keating*
CCSM Executive Director
909-624-3012
www.claremontmusic.org
…On Thu, Sep 2, 2021 at 6:06 PM Kevin Doren ***@***.***> wrote:
@ChorusJam <https://github.com/ChorusJam> I'm glad you got it working.
The raspberry pi will send its access URL with IP address to urlrelay.com
on each boot. So, even if IP address changes, you should still be able to
access via urlrelay.com/go.
The /boot/payload/ directory only exists after burning the microSD card,
but before first boot. Any files there will be copied to the root partition
on first boot, then the /boot/payload/ directory is deleted. A few files
are seeded there for possible editing if you want to make changes without
booting. But you could place any file there and it will be copied.
If you're burning multiple SD cards, it's very handy to be able to
customize without booting. One use is to give each card a different NODE_ID
by editing /boot/payload/etc/urlrelay/urlrelay.conf. Another is to set up
autostart for jamulus or other jamming app.
On my system, after burning a micro SD card using balenaEtcher, I need to
unplug/re-plug my microSD-to-USB adapter in order to see the /boot
partition.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#113 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATCSWEIANHV2QLSM6PH2BFLUAANQPANCNFSM5DKCQOLA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
Hi all, |
Beta Was this translation helpful? Give feedback.
-
|
@yoyomatt4cello @ChorusJam I burn a lot of cards, and balenaEtcher has always been reliable for me using zip files directly without unzipping. If your burned cards don't work, it's likely a problem with either the cards themselves, or the burner hardware.
|
Beta Was this translation helpful? Give feedback.
-
|
@kdoren I was using the Sandisk Extreme in this case. And the SD card slot from my MacMini, so no USB adaptor. Anyway, since using the img works for me, I will continue this way. thx |
Beta Was this translation helpful? Give feedback.
-
|
Good to know!
I have been using the "Ultra" SD cards. Maybe that is the issue:
https://www.amazon.com/gp/product/B089DPCJS1/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1
I will order the Kingston mobilite per your suggestion. The accompanying
plastic adapters that sometimes come with the SD cards have been hit and
miss for me. I've been relying pretty heavily on the Vilros USB adapter
<https://vilros.com/blogs/getting-started/vilros-retro-pi-kit-usb-stick>
that came with one of my original pi sets. Perhaps I've burned it out.
Thanks again,
*Matthew Keating*
CCSM Executive Director
909-624-3012
www.claremontmusic.org
…On Fri, Sep 3, 2021 at 4:44 AM Kevin Doren ***@***.***> wrote:
@yoyomatt4cello <https://github.com/yoyomatt4cello> @ChorusJam
<https://github.com/ChorusJam> I burn a lot of cards, and balenaEtcher
has always been reliable for me using zip files directly without unzipping.
If your burned cards don't work, it's likely a problem with either the
cards themselves, or the burner hardware.
1. SD cards are not all the same. I personally use Sandisk Extreme
with excellent results. My limited experience with off-brand cards has not
been so good.
2. SD card USB adapters are not all the same. I mostly burn using
Kingston Mobilite Plus (https://www.amazon.com/gp/product/B085P5FDXQ)
, and have also had good results with an older adapter from iogear. I have
had inconsistent results with some off-brand adapters.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#113 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATCSWEO5PZQOCNIYYGKGU2TUACYKDANCNFSM5DKCQOLA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
Sandisk ultra should also burn reliably. I would stay away from no-name brands though. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Kevin,
I picked up a Kingston Mobilite Plus per your recommendation as well as a
brand new SanDisk ultra 16GB SD. The Kingston completed the flash
"successfully" according to Balena Etcher. The Pi unfortunately would
still not boot up. I ordered several Sandisk Extreme 32 GB cards and tried
them with the Kingston. They work great and booted up just fine.
Hard for me to believe that 5 brand new SanDisk Ultra 16GB cards are all
bad eggs. I've tried re-etching these with different adapters, computers,
etc, and nothing seems to work. Am I missing something simple here? Do I
need to re-format the SD a specific way before it is etched? I have around
30 students using jamboxes with ultra 16GB cards without issue, but
suddenly I cannot get any new ultra cards to work properly.
Thanks in advance,
Matt
*Matthew Keating*
CCSM Executive Director
909-624-3012
www.claremontmusic.org
…On Fri, Sep 3, 2021 at 10:36 AM Kevin Doren ***@***.***> wrote:
Sandisk ultra should also burn reliably. I would stay away from no-name
brands though.
I have had problems with off-brand adapters.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#113 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATCSWEJ6UEXQFNOVRQFPUUTUAEBQDANCNFSM5DKCQOLA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
I have a few ultra cards, and they work fine for me. I prefer the Sandisk Extreme cards because they burn and boot faster, and have been extremely reliable for me. But the ultra cards should work. You shouldn't need to do any special formatting, etc, that is BalenaEtcher's job. You've tried many combinations, but the failure always travels with the card. So card must be bad, which doesn't make sense because it validates OK after burning. I presume you've tried different Pi's also? One test you could try: Take a known good ultra card (from a working box), and re-burn it at the same time you re-burn a new "bad" card. only difference is new vs old ultra card. I'm guessing new one will still fail, and old one will still work. Only hypothesis that fits your symptoms: You have 5 ultra cards all from a bad batch that got past Sandisk QA. Failure mode is that the card validates after burning (which is how it passed QA) but there is some other problem (not tested by QA) that causes it to fail to boot on the Pi. Hard to believe, but I see no other explanation. |
Beta Was this translation helpful? Give feedback.
-
|
Kevin,
Thanks again for your assistance. I am suddenly doubting that there is a
card issue as one of the San Disk 32 GB Extremes that I purchased and
recently etched is now having the same issue as the 5 Ultras. I also just
took a working SD card to re-etch it with your recent update and noticed
that the card is no longer working with the Pi. Perhaps this is a URL relay
issue? I have been changing the node ids through the No VNC url relay
access after the initial etching process, but perhaps the jamboxes are not
registering properly with the basic image settings before I change the node
ID. I will attempt to interface with the jambox directly with a keyboard,
mouse ,and physical display to see what things look like.
Thanks again! I am a cellist by trade and new to Linux, RPis, and basic
programming skills.
Kind Regards,
Matt
*Matthew Keating*
CCSM Executive Director
909-624-3012
www.claremontmusic.org
…On Tue, Sep 21, 2021 at 12:31 AM Kevin Doren ***@***.***> wrote:
I have a few ultra cards, and they work fine for me. I prefer the Sandisk
Extreme cards because they burn and boot faster, and have been extremely
reliable for me. But the ultra cards should work.
You shouldn't need to do any special formatting, etc, that is
BalenaEtcher's job.
You've tried many combinations, but the failure always travels with the
card. So card must be bad, which doesn't make sense because it validates OK
after burning. I presume you've tried different Pi's also?
One test you could try: Take a known good ultra card (from a working box),
and re-burn it at the same time you re-burn a new "bad" card. only
difference is new vs old ultra card. I'm guessing new one will still fail,
and old one will still work.
Only hypothesis that fits your symptoms: You have 5 ultra cards all from a
bad batch that got past Sandisk QA. Failure mode is that the card validates
after burning (which is how it passed QA) but there is some other problem
(not tested by QA) that causes it to fail to boot on the Pi. Hard to
believe, but I see no other explanation.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#113 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATCSWENS3K6XAOVZISVLUQDUDAYGTANCNFSM5DKCQOLA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
@yoyomatt4cello "I can't get into the box" is a different problem than "the SD card is bad". When you power the box on, if the card is good and the box is booting, you'll see a number of long bursts of green LED activity over many seconds. I think I can figure out your IP address, and here is what I see: There are 3 boxes (1,2,6) currently registered from your IP, and 3 others (3,4,5) that have moved to different IPs. Currently: Moved: nodeId's 3,4,5 are now on different sourceIp's, so must have moved. The redirect via urlrelay.com has been quite reliable, and has been used by a lot of people. There have been a couple of strange edge cases where router config issues caused problems. Yours has worked in the past, so this seems unlikely. urlrelay.com does a redirect to the local access url of the Pi on your local network. I've listed the url's below, so you should be able to get into the Pi by using those url's directly in your browser. However be aware that those urls could change it/when your router assigns different IP addresses to the raspberry pi's. If that doesn't work, there's the possibility that your router is blocking traffic between your browser and the Pi. This could happen, for example, if your browser is on a wireless "guest" network and your router, by design, is blocking traffic to the rest of your local network. The remedy in that case is to use a browser on a device that has connectivity, either on a non-guest network, or even better, on the same wired network as the raspberry pi. NODE_ID should be changed immediately after flashing, before booting, by editing file /payload/etc/urlrelay/urlrelay.conf |
Beta Was this translation helpful? Give feedback.
-
|
Kevin,
This is really helpful. Embarrassed at my novice skills but also glad that
the SD cards are not at issue. There are plenty of green LED bursts at the
Rj-45 port.
For months I have been etching the jamboxes with the image file, booting up
the jambox, accessing the jambox via URL relay, and then changing the NODE
ID via text file in etc. How would I edit the text file before boot as you
suggested?
There must be a jambox registered as "1" not allowing my new jamboxes to
register properly.
Thanks again for your help,
*Matthew Keating*
CCSM Executive Director
909-624-3012
www.claremontmusic.org
…On Wed, Sep 22, 2021 at 12:38 PM Kevin Doren ***@***.***> wrote:
@yoyomatt4cello <https://github.com/yoyomatt4cello> "I can't get into the
box" is a different problem than "the SD card is bad".
Not always easy to tell them apart, though.
When you power the box on, if the card is good and the box is booting,
you'll see a number of long bursts of green LED activity over many seconds.
I think I can figure out your IP address, and here is what I see:
There are 3 boxes (1,2,6) currently registered from you IP, and 3 others
(3,4,5) that have moved to different IPs.
Currently:
nodeId url
1 http://192.168.1.125:6080/?password=jambox (this box had nodeId=8 at one point, now nodeId=1)
2 http://192.168.1.199:6080/?password=jambox
6 http://192.168.1.110:6080/?password=jambox
Moved: nodeId's 3,4,5 are now on different sourceIp's, so must have moved.
The redirect via urlrelay.com has been quite reliable, and has been used
by a lot of people. There have been a couple of strange edge cases where
router config issues caused problems. Yours has worked in the past, so this
seems unlikely.
urlrelay.com does a redirect to the local access url of the Pi on your
local network. I've listed the url's below, so you should be able to get
into the Pi by using those url's directly in your browser.
If that doesn't work, there's the possibility that your router is blocking
traffic between your browser and the Pi. This could happen, for example, if
your browser is on a wireless "guest" network and your router, by design,
is blocking traffic to the rest of your local network. The remedy in that
case is to use a browser on a device that has connectivity, either on a
non-guest network, or even better, on the same wired network as the
raspberry pi.
NODE_ID should be changed immediately after flashing, before booting, by
editing file /payload/etc/urlrelay/urlrelay.conf
However you have done that successfully in the past, so it doesn't seem
likely to the the problem here.
It's possible to change after first boot, but to do that, you need to get
into the box first, so I don't recommend it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#113 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATCSWEK7OIX3SGGAESG4243UDIWDNANCNFSM5DKCQOLA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
After flashing with, you'll need to unplug the USB SD card adapter, then re-plug. Before first boot, there is a directory on the SD card "boot" volume named /payload. In the "boot" drive, navigate to /payload/etc/urlrelay/urlrelay.conf If you have multiple boxes on same local network with same NODE_ID (i.e. default NODE_ID=1), So it's best to set the NODE_ID before booting, and it's easier and faster too. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, Kevin. This is a big help.
I'm using a mac at the school office, so I tried what you suggested with an
equivalent program and it worked the first time! The second card was not
successful, unfortunately.
I went home to try it out on my PC and am getting the same error message
that I was getting at the school:
[image: No device with ID.png]
I tried what you suggested with notepad++ and made sure that I saved the
new node ID each time:
[image: Node id.png]
Thanks again for your willingness to help. I really would be happy to
donate or help pay for your AWS server that is hosting all of this. I hate
bothering you with seemingly novice questions; I'm just not sure what to do.
Best,
*Matthew Keating*
CCSM Executive Director
909-624-3012
www.claremontmusic.org
…On Wed, Sep 22, 2021 at 4:40 PM Kevin Doren ***@***.***> wrote:
After flashing with, you'll need to unplug the USB SD card adapter, then
re-plug.
That should cause Windows to see a drive called "boot" ( the boot
partition of the SD card).
Before first boot, there is a directory on the SD card "boot" volume named
/payload.
The "boot" volume can be seen and edited in Windows (unlike the linux /
volume)
Any files in /payload will be copied into to linux / volume at first boot,
then /payload is erased.
This is the best way to customize NODE_ID, and also other config items
such as JAMULUS_SERVER.
https://github.com/kdoren/jambox-pi-gen#customizable-settings
In the "boot" drive, navigate to /payload/etc/urlrelay/urlrelay.conf
edit this file (I suggest notepad++ https://notepad-plus-plus.org/ )
change NODE_ID to something different, save, and safely eject the SD card
(right-click eject "boot" in windows explorer).
If you have multiple boxes on same local network with same NODE_ID (i.e.
default NODE_ID=1),
then the most recent one to register will claim that ID with urlrelay.com.
You won't be able to get to the other box via urlrelay.com until it
re-registers.
So it's best to set the NODE_ID before booting, and it's easier and faster
too.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#113 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATCSWEL573FCAGZ6XBMJG53UDJSOJANCNFSM5DKCQOLA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
Your image (png) files didn't upload, so I can't see them. I looked at the traffic logs, and I see attempts to access id=9, but no box with id=9 ever registers (although id=7 was apparently successful, and you were able to access it). There's also a box with id=8 which is new. So it would appear that there is a problem with box id=9, either its hardware or network connection, or the box does not think it has id=9 so it's registering as id=1. Things to try:
|
Beta Was this translation helpful? Give feedback.
-
|
Answers in blue below:
*Matthew Keating*
CCSM Executive Director
909-624-3012
www.claremontmusic.org
On Thu, Sep 23, 2021 at 2:30 AM Kevin Doren ***@***.***> wrote:
Your image (png) files didn't upload, so I can't see them.
I looked at the traffic logs, and I see attempts to access id=9, but no
box with id=9 ever registers (although id=7 was apparently successful, and
you were able to access it). There's also a box with id=8 which is new. Yes,
7 was the last successful box to register with my prior method of booting
first, acessing via url relay, and then changing the text file NODE ID
directly on the box to 7. Box 8 is the first box that I tried to use your
newly recommended method via the payload directory, which worked perfectly.
So it would appear that there is a problem with box id=9, either its
hardware or network connection, or the box does not think it has id=9 so
it's registering as id=1. I think I have ruled out the hardware and
network connection as issues.
Things to try:
1. After flashing, editing /payload/etc/urlrelay/urlrelay.conf, and
ejecting - but before booting, double-check that the file is written
correctly. Plug it back in and read the file again. It's unlikely, but
there can be cases where the changes don't get properly written to SD card
(if that heppened, you would be able to get into it as id=1). That's why I
recommend the "safe eject" method of right-click on the USB drive, then
"eject". Yes, I tried this several times before my last email as you
instructed being careful to properly eject the boot drive both on my PC and
mac.
2. Does the problem travel with the card or with the box? take the
card from a known good box (id=7) and put it in the "bad" box, which should
now take over id=7 if it can boot and connect to network. if you can't get
into the "bad" box with good card id=7, there is something wrong with the
box or its network connection. I've determined that the problem
travels with the card.
3. Take the card from "bad" box id=9 and put it in known good box
(id=7). if the card is good, that box should now work as id=9. If it
doesn't work, something is wrong with card. id=9 SD card did not work
on several "good" boxes.
4. if the "bad" box is the only box currently running on your local
network, try getting in with this url:
http://jambox.local:6080/?passoword=jambox
this is not guaranteed, but is likely to work from windows, not sure
about mac.
if you have more than one box running, it's indeterminate which one
you will get.
if you can get in this way, you can look at file
/etc/urlrelay/urlrelay.conf to verify/change NODE_ID setting. This
link worked with the id=9 SD card! Woo hoo! It took about 10 minutes of
trying, but I finally was routed to the NOVNC login window and then was
prompted to enter a password. I entered "jambox" and connected to the Pi
just fine. I immediately checked the file at /etc/urlrelay/urlrelay.conf
to verify/change NODE_ID setting and curious enough, the NODE ID was
displaying "id=9" just like I had entered in notepad++. Next, I tried
accessing the jambox with "id=9" from a separate computer on the same
network and I was able to access it just fine! Do you have any idea why
URL relay doesn't seem to be registering the id properly upon initial
set-up? I have never seemed to have this problem before which is why I was
convinced earlier that I must be getting bad SD cards. In any case, I'm
glad this is working now and will resume my project of updating our student
jamboxes to your latest image release.
Thank you, Kevin,
Matt
…
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#113 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATCSWEMWUZU42K6R4ZZJAHTUDLXSDANCNFSM5DKCQOLA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
|
the syntax in file urlrelay.conf is i.e.: Why did it think NODE_ID was not set, even though you edited the file? On windows, I edit such files with notepad++, with line endings set to "Unix" (Edit -> EOL Conversion -> Unix) I prefer editing SD card before first boot, but you could also boot the box with stock image, in which case it will claim id=1. edit, save, then reboot, or restart urlrelay service: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I'll check it out.
I will try the syntax settings as you mentioned.
I actually prefer booting the box with the stock image, letting it claim
id=1 and then navigating with the GUI to the individual config files to
make changes that way. I had been doing it this way for months before
really beginning to use the NODE_ID feature. We have enough jamboxes in use
now that are not just staying at students homes, but are sometimes coming
to our campus. I started reimaging boxes one by one in the last several
weeks in order to apply your latest image update (which is fantastic by the
way - the QAS Mixer is SO easy for folks to use) and to begin cataloging
the boxes with unique NODE IDs so that there will never be an access issue
when multiple boxes are on campus at the same time. My problem is that
every recent re-image in the last week or so no longer seems to properly
claim id=1 upon the initial boot and I consistently receive a "failed to
connect to server" error message when trying to connect.
Hopefully I will be able to navigate to these recent imaged boxes with your
local id link suggestion from the previous email. That worked this last
time at least.
Thanks so much again for your assistance!
*Matthew Keating*
CCSM Executive Director
909-624-3012
www.claremontmusic.org
…On Thu, Sep 23, 2021 at 10:54 AM Kevin Doren ***@***.***> wrote:
the syntax in file urlrelay.conf is i.e.:
NODE_ID=9
If the service script thinks that NODE_ID is not set, it will use default
value of "1". I think that's what happened in your case.
Why did it think NODE_ID was not set, even though you edited the file?
Likely answer is a syntax problem, maybe an extraneous (and possibly
invisible) character got inserted either by you or by your editor.
Most editors have a way to display even non-printing characters, so you
could check that.
In notepad++, this is enabled with: View -> Show Symbol -> Show All
Characters
On windows, I edit such files with notepad++, with line endings set to
"Unix" (Edit -> EOL Conversion -> Unix)
I prefer editing SD card before first boot, but you could also boot the
box with stock image, in which case it will claim id=1.
Get into the box using id=1, then launch editor as follows:
sudo leafpad /etc/urlrelay/urlrelay.conf
edit, save, then reboot, or restart urlrelay service:
sudo systemctl restart urlrelay
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#113 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATCSWEONO4XRKC7SDPOVD5DUDNSV5ANCNFSM5DKCQOLA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
-
Hi, I just discovered, that with Jamulus Autostart, VNC to the Jambox is not working anymore. Is this the expected behaviour?
When I urlrelay.com/go the Jambox, it shows the VNC login Window, but when trying to login, after time out it shows the red label "Failed to connect to Server"
Before the Autostart setting, everything was working as expected.
The reason why I would still like to VNC to the Pi is for changing the configuration settings. Since the device will run remote at a chorus member location, I don't have the option to change the settings by using a card reader.
thx a lot!
Beta Was this translation helpful? Give feedback.
All reactions