No Target Host Mappings Defined about corsproxy HOT 3 CLOSED

So given you followed the procedure and it worked this time I guess we can close your original issue #1?

As the instructions say, you can enter mappings either with spaces between them, or on different lines, etc so I doubt you have that incorrect. It is far more likely you have placed the configuration file in the wrong place. Given you have run the program as user "pi" then the config file should be at /home/pi/.config/corsproxy. Please check that. Note that the Linux shell aliases ~ as a shorthand for the home directory of the user, i.e. /home/pi in this case.

from corsproxy.

"So given you followed the procedure and it worked this time I guess we can close your original issue #1?"

still have that issue on the other sd card. im guessing updating from wheezy to jessie to stretch to then buster something has gone astray. but yes close it
I started with a new image and everything works as expected so something wrong with the other image. going to have to try and get my other software running on this image... (seems to be just as challenging)

the .config/corsproxy was in root.
have changed it to /home/pi/.config/corsproxy now and works. cheers
im guessing since I done that step later I wasn't in the right directory before issuing the command...

thanks for all your help

from corsproxy.

If you were logged in as user pi and you edited that file, e.g. vim ~/.config/corsproxy, then it would have been pointing to the correct file. You must have done it as root. Generally, avoid doing much in root on Linux systems. Work as your normal user and just use sudo for the occasional root command when needed.

from corsproxy.