What url does the shortcut save, with http:// or https:// ?
The next gui version will support https, but you need to supply a certificate to enable it. The default will be http only.
This is another big mess where google's (and other browser manufacturer companies') initiatives for "https only" will fall back on web apps that want to run in local context only. We (as in my employer and me as the driving force to want to develop/enhance code with local virtual machines) got around that by setiing up a local CA and signing local certificates with the CA key. This is a rather complicated process (it has to be introduced to the OS) and it took me about 4-5 A4 pages on our local wiki to explain the process to my colleagues. Let alone the time to develop this process. Not acounting for EVERY employee has to jump throgh these hoops.
Contrary to the former "caching" problem I cannot point out any easy answer here. I wish I could!!!
Enabling https with a certificate will almost certailny will have the requirement that that your app -
This is becoming a real problem for privately hosted web services. It will become worse rather than better, I fear.
Contrary to the former "caching" problem I cannot point out any easy answer here. I wish I could!!!
Enabling https with a certificate will almost certailny will have the requirement that that your app -
- runs under a FQDN, a fully qualified domain name, one which does not change, i.e. "my.camilldadpsp.tld"
- is reachable from the internet from this FQDN
- has some kind of certificate issuing agency behind it that will
- issue/renew certificates (for free?!)
- can automate that process, otherwise that will be a real hassle for you, letsencrypt does epxpire certs after 3 months (but at least its free)
- you as a "webservice" provider understand all that and...
- your FQDN is publicly visible, at least with some sort of "dyndns" service, otherwise the CA will not issue a certificate for you.
This is becoming a real problem for privately hosted web services. It will become worse rather than better, I fear.
For moOde we included an experimental HTTPS mode in our most recent release. It's pretty simple on the back-end to auto-generate a self-signed cert for the web server which in our case is NGINX. If user changes the player name (host name) then a new cert is auto-generated, no problem.
The challenge is getting the self-signed cert into the client OS certificate store. It's a multi-step manual process that varies depending on the OS and not "user friendly". On MacOS for example, dbl click the cert opens the Keychain app for import but requires entering logon password multiple times before cert is added, then there is another step to mark it as a trusted cert. Once thats done Browser to moOde connection is HTTPS including CamillaGUI.
We are looking for feedback from our user community on steps for adding self-signed cert to Windows, Linux, IOS and Android.
Gotta start somewhere but IMO whats really needed is for the group(s) working on certificate infrastructure to develop a solution for local hosts thats as trustworthy and easy to admin as that for Internet hosts.
The challenge is getting the self-signed cert into the client OS certificate store. It's a multi-step manual process that varies depending on the OS and not "user friendly". On MacOS for example, dbl click the cert opens the Keychain app for import but requires entering logon password multiple times before cert is added, then there is another step to mark it as a trusted cert. Once thats done Browser to moOde connection is HTTPS including CamillaGUI.
We are looking for feedback from our user community on steps for adding self-signed cert to Windows, Linux, IOS and Android.
Gotta start somewhere but IMO whats really needed is for the group(s) working on certificate infrastructure to develop a solution for local hosts thats as trustworthy and easy to admin as that for Internet hosts.
Last edited:
@HenrikEnquist - regarding populating the Capture & Playback drop down list. Could CamillaDSP possible cash this content before closing with error? And then have the back-end fall back to reading from cash/file when it fail realtime comunication with CamillaDSP?
I actually have no way of knowing that, the "403: Forbidden" screen does not show the offending URL. There is no access to shortcut properties, I can only long-press on the shortcut icon to remove it.
Indeed, when I put the CamillaGUI URL with "http://" in the browser, the latter removes the prefix, and what I see in the URL window is:
192.168.0.X:5000/gui/index.html
Note that:
1) Other chrome shortcuts do work. For example I have no problem with the shortcut to the LMS Material plugin interface (which does not support https):
192.168.0.Y:9000/material
2) The problem occurs only on android. No problem whatsoever on my linux desktop computer.
I suspect that the issue is related to the fact that CamillaGUI is based on React. Unfortunately, I am not familiar with React, and I have no idea how to solve the problem.
Yes that makes sense, I have added this for the next version.
Ah right, it's not a normal bookmark. I don't know how this works, but I'll take a look when I have some time.
Yeah it's a mess, I think the only reasonable thing for camillagui is to continue with http only as default. I added the https support for those that want it and know enough to be able to figure things out themselves.
That's more than the entire camillagui documentation 😛
It's not reasonable to include something like this (and frankly I don't know this stuff well enough to write it, would take forever!).
@mevang - I use this functionality daily with the DuckDuckGo browser on Samsung phone with CamillaGUI.
It also function with official Firefox browser.
The problem seem to stem from anything Crome based. While Firefox will use the the URL and page name Chrome based browsers see the page as a React App. And problebly screw up the URL in antemt to be clever.
Edit: You could try implement opening CamillaDSP from Material Skin as described here:
https://github.com/StillNotWorking/...in/materialskin#custom-menus-in-material-skin
Last edited:
I think the problem is that the "start_url" in the manifest is incorrect, but I don't know yet what it should be set to. It's defined here:
https://github.com/HEnquist/camilla...475e2ce6e6c7d10482d4/public/manifest.json#L21
https://github.com/HEnquist/camilla...475e2ce6e6c7d10482d4/public/manifest.json#L21
Then I don't get how Firefox are able solve this if path on server is wrong? I think this is browser related. I'm guessing FF first test connection on 443 and then goes to 80 when it fails. While Chrome are forcing cryptation.
https://superuser.com/questions/565...tomatic-redirect-from-http-to-https-in-chrome
https://superuser.com/questions/565...tomatic-redirect-from-http-to-https-in-chrome
On my android 10 phone, DuckDuckGo refuses to create a shortcut to CamillaGUI, Firefox creates the shortcut but it produces the 403 error.
On my android 11 tablet, both DuckDuckGo and Firefox shortcuts do work, with chrome I get the 403 error.
Maybe the issue is also related to to android version and local security policies.
In any case, this is a very minor issue I can live with.
Thanks to everyone who replied to my posts.
On my android 11 tablet, both DuckDuckGo and Firefox shortcuts do work, with chrome I get the 403 error.
Maybe the issue is also related to to android version and local security policies.
In any case, this is a very minor issue I can live with.
Thanks to everyone who replied to my posts.
@DEQ+TheEnd, this is really interesting, I will give it a try.
To be honest, it is 80% screenshots, to make my less technically oriented colleagues be able to follow step by step 🙂
Would someone please help me troubleshoot camillagui v2?
I can get CamillaDSP to run ok:
(camilladsp2) dsp 0:26 ~/camilladsp/camillagui % ./camilladsp ./configs/headphones.yml
2024-02-19 00:26:46.791675 INFO [src/bin.rs:683] CamillaDSP version 2.0.2
2024-02-19 00:26:46.791728 INFO [src/bin.rs:684] Running on macos, aarch64
When I try to run camillagui:
(camilladsp2) dsp 0:27 ~/camilladsp/camillagui % python main.py
...
File "/Users/dsp/camilladsp/camillagui/backend/settings.py", line 148, in <module>
config = get_config(CONFIG_PATH)
^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/dsp/camilladsp/camillagui/backend/settings.py", line 69, in get_config
config["statefile_path"])
~~~~~~^^^^^^^^^^^^^^^^^^
KeyError: 'statefile_path'
I am not sure where to start troubleshooting this. Would someone please help with this?
I can get CamillaDSP to run ok:
(camilladsp2) dsp 0:26 ~/camilladsp/camillagui % ./camilladsp ./configs/headphones.yml
2024-02-19 00:26:46.791675 INFO [src/bin.rs:683] CamillaDSP version 2.0.2
2024-02-19 00:26:46.791728 INFO [src/bin.rs:684] Running on macos, aarch64
When I try to run camillagui:
(camilladsp2) dsp 0:27 ~/camilladsp/camillagui % python main.py
...
File "/Users/dsp/camilladsp/camillagui/backend/settings.py", line 148, in <module>
config = get_config(CONFIG_PATH)
^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/dsp/camilladsp/camillagui/backend/settings.py", line 69, in get_config
config["statefile_path"])
~~~~~~^^^^^^^^^^^^^^^^^^
KeyError: 'statefile_path'
I am not sure where to start troubleshooting this. Would someone please help with this?
@DEQ+TheEnd Thanks for that steer. For some reason statefile path was missing. Maybe I deleted it when I was merging config/s from camilladsp v1? Not sure.
CamillaGUI is running now!
I do get an error message when I select 'Files' tab:
ERROR:root:CamillaDSP runs without state file and is unable to persistently store config file path
ERROR:root:CamillaDSP runs without state file and is unable to persistently store config file path
~/camilladsp/camillagui/config % more camillagui.yml:
---
camilla_host: "127.0.0.1"
camilla_port: 5001
port: 5002
bind_address: "0.0.0.0"
config_dir: "~/camilladsp/camillagui/configs"
coeff_dir: "~/camilladsp/camillagui/coeffs"
default_config: "~/camilladsp/camillagui/config/Default.yml"
log_file: "~/camilladsp/camillagui/logs/camilladsp.log"
statefile_path: "~/camilladsp/camillagui/statefile.yml"
I don't see a statefile.yml anywhere in the downloaded zip file. What should be its contents?
CamillaGUI is running now!
I do get an error message when I select 'Files' tab:
ERROR:root:CamillaDSP runs without state file and is unable to persistently store config file path
ERROR:root:CamillaDSP runs without state file and is unable to persistently store config file path
~/camilladsp/camillagui/config % more camillagui.yml:
---
camilla_host: "127.0.0.1"
camilla_port: 5001
port: 5002
bind_address: "0.0.0.0"
config_dir: "~/camilladsp/camillagui/configs"
coeff_dir: "~/camilladsp/camillagui/coeffs"
default_config: "~/camilladsp/camillagui/config/Default.yml"
log_file: "~/camilladsp/camillagui/logs/camilladsp.log"
statefile_path: "~/camilladsp/camillagui/statefile.yml"
I don't see a statefile.yml anywhere in the downloaded zip file. What should be its contents?
Last edited:
Perhaps just create an empty one and see if C writes in it... I have also problems main these files work - maybe its a permission issue...
//
//
Starting camilladsp with the -w argument this file will be created empty.
Purpose of this file is to store volume setting and which configuration to use. Meaning which file we select while pressing the star on Files tab.
You can download an example from my rep
https://github.com/StillNotWorking/...rsion-2-install-script-for-rpi-os-lite-64-bit
Purpose of this file is to store volume setting and which configuration to use. Meaning which file we select while pressing the star on Files tab.
You can download an example from my rep
https://github.com/StillNotWorking/...rsion-2-install-script-for-rpi-os-lite-64-bit
Thank you for the suggestion. It didn't fix the issue.
I also tried @DEQ+TheEnd 's suggestion of starting camilladsp with -w argument, as well as trying the file on linked github. Still having the error.
Setting the statefile.yml permissions to 777 didn't help.