ProScan: Official Software Thread

[ToddWilkinson]

Thank You Bob For ProScan, I'd be lost wihout it!

 

[Steve_eo]

I'm having trouble with a newly downloaded ProScan launching the Web Server.
I've installed the RadioFeed program and it works perfectly.
But if I shutdown RadioFeed and just try running ProScan WebServer, I get the error "Web Server: Set The Input Sound Device To A Valid Input Located in the Audio Control Tab".
I am using the same URL based "Input Sound Device" located in the Audio Control tab as I am with the RadioFeed program.....so I know it works.....yet when I switch to using the ProScan WebServer, it complains.....
I've reached out to Bob Aune but he's out of ideas....
Anyone?

 

[ProScan]

I'm having trouble with a newly downloaded ProScan launching the Web Server.
I've installed the RadioFeed program and it works perfectly.
But if I shutdown RadioFeed and just try running ProScan WebServer, I get the error "Web Server: Set The Input Sound Device To A Valid Input Located in the Audio Control Tab".
I am using the same URL based "Input Sound Device" located in the Audio Control tab as I am with the RadioFeed program.....so I know it works.....yet when I switch to using the ProScan WebServer, it complains.....
I've reached out to Bob Aune but he's out of ideas....
Anyone?

You're email is different. Basically you are trying to get the SDS200 Ethernet audio to work with ProScan
This is your original email

I've just downloaded the latest Proscan s/w. Both the ProScan 20.7 and the RadioFeed 6.1.
I can get the RadioFeed to work flawlessly. But the ProScan always gives me an error message regarding turning on audio in the Audio Control tab.
I'm using URL in both s/w. I have a SDS200.
I can't be the only one that has trouble with this I suspect.

 

[buddrousa]

If I was to take a wild guess most remote audio issues may be caused by not setting the correct audio source piked in the remote server and the web server as they are set on an individual basis.

 

[fxdscon]

I am using the same URL based "Input Sound Device" located in the Audio Control tab as I am with the RadioFeed program.....so I know it works.....yet when I switch to using the ProScan WebServer, it complains.....

-
When you switch to using the ProScan webserver, are you also setting the input sound device in the webserver tab after clicking the audio tab?

I can't be the only one that has trouble with this I suspect.

-
I use the SDS200 extensively with the ProScan web server and never had a problem myself. The only problem I ever recall others having was the user not setting the audio input in the correct area..... the web server tab. ProScan has a very large customer base and if there was a problem with the software, there would be many instances of that issue in this forum.

 

[Steve_eo]

-
When you switch to using the ProScan webserver, are you also setting the input sound device in the webserver tab after clicking the audio tab?


View attachment 137455


-
I use the SDS200 extensively with the ProScan web server and never had a problem myself. The only problem I ever recall others having was the user not setting the audio input in the correct area..... the web server tab. ProScan has a very large customer base and if there was a problem with the software, there would be many instances of that issue in this forum.

You are a genius!
I just didn't see that I had to setup audio again....as you indicated. Thank you very much!

 

[morrisr3nd]

Alright, I've got a little issue. I just installed Proscan on a computer. It will recognize my scanners (SDS100, BCD436HP) when I selected the proper port to view the scanner screen. However when I went to download new Favorites (After of course putting them into USB Mass Storage Mode) it would not recognize the port. It says "CHECK DRIVER" next to the port number. I don't get it. I am running Windows 10. I've had this computer for some time and just wanted to use it while traveling just for my scanners. A little help would be greatly appreciated.

 

[ProScan]

Alright, I've got a little issue. I just installed Proscan on a computer. It will recognize my scanners (SDS100, BCD436HP) when I selected the proper port to view the scanner screen. However when I went to download new Favorites (After of course putting them into USB Mass Storage Mode) it would not recognize the port. It says "CHECK DRIVER" next to the port number. I don't get it. I am running Windows 10. I've had this computer for some time and just wanted to use it while traveling just for my scanners. A little help would be greatly appreciated.

The check driver message next to the port menu shows when you click on the serial port Auto Detect. and the serial port is non functional when the scanner is in Mass Storage mode.
In the Favorites editor, click on 'Scanner Read' A dialog should appear with the scanner showing.

 

[DannyBoy2k]

Due to my ISP blocking port 80, I've had to generate my Let's Encrypt certificate manually using their DNS validation method. That process went OK, but, when I try to use them in ProScan, I'm getting the following error:


I have the following files in my Certbot directory (C:\Certbot\archive\<domain>\):
cert1.pem
chain1.pem
fullchain1.pem
privkey1.pem

I've tried using both cert1.pem and fullchain1.pem for the cert and privkey1.pem for the private key, but the ProScan webserver doesn't appear to like them. Any help is appreciated!

Thanks,
Dan

 

[DannyBoy2k]

Ah, I was able to answer my own question. It appears they started changing to a new key format in late 2022.

Getting a RSA privkey from the letsencrypt generated pem

That makes sense. The documentation falls short in their explanation. If you generate a random private key, you should use that same private key in the entire process. But there is no good reason not to use the private key generated by Certbot. It's just very weird your OpenSSL doesn't work...

community.letsencrypt.org

I was able to use the --key-type rsa option and regenerate my cert and key in the format ProScan expects.

~Dan

 

[fxdscon]

Any help is appreciated!

-
You can "port forward" your port 80 for the IP address of the computer running Proscan. It just takes a few seconds to get the certificate, then just delete that port forward rule as soon as it's done.

 

[belvdr]

-
You can "port forward" your port 80 for the IP address of the computer running Proscan. It just takes a few seconds to get the certificate, then just delete that port forward rule as soon as it's done.

If the ISP is blocking the inbound ports, it won’t be able to verify.

 

[DannyBoy2k]

If the ISP is blocking the inbound ports, it won’t be able to verify.

Yes, exactly this. It turns out Let's Encrypt changed their default key type per the link I put above. I was able to just regenerate my key and cert to use RSA keys and all is well.

Thanks, all.

~Dan

 

[fxdscon]

If the ISP is blocking the inbound ports, it won’t be able to verify.

DNS validation to acquire the keys occurs on port 80. A temporary port forward is all that's necessary to validate and acquire the keys. The incoming "https" requests to access the server and see the secure certificate don't use port 80.

 

[fxdscon]

Ah, I was able to answer my own question. It appears they started changing to a new key format in late 2022.

Hmmmm....................

These are the keys sent to me from LetsEncrypt:

 

[DannyBoy2k]

DNS validation to acquire the keys occurs on port 80. A temporary port forward is all that's necessary to validate and acquire the keys. The incoming "https" requests to access the server and see the secure certificate don't use port 80.

No, DNS validation requires that your DNS provider be able to update a TXT record with a known value. Setting that proves you own the DNS domain entry with the DNS provider, which satisfies Let's Encrypt. Freemyip.com, which is what I use for DynDNS, allows me to do that.

Challenge Types

When you get a certificate from Let’s Encrypt, our servers validate that you control the domain names in that certificate using “challenges,” as defined by the ACME standard. Most of the time, this validation is handled automatically by your ACME client, but if you need to make some more complex...

letsencrypt.org

I admit I did not verify that Comcast does _actually_ block port 80 and 443 for home IP addresses, but that's what the Interwebs' consensus appears to be.

~Dan

 

[DannyBoy2k]

Hmmmm....................

These are the keys sent to me from LetsEncrypt:

View attachment 137521

I'm not sure if ProScan is doing anything under the hood to convert anything or even perhaps using the --key-type RSA option or if the HTTP validation method causes the Certbot to use that option by default.

Per the link I referenced, the manual method, which I used for DNS validation, appears to now default to ECDSA keys:

Yeah, I'm guessing that what happened is certbot got upgraded to version 2, and how whatever manual process they're using is working means that certbot is seeing it a new certificate each time (so not keeping the key type from last time), so now that certbot is using ECDSA keys by default their process doesn't work anymore.
So just adding --key-type rsa to the command they're using to generate the key with certbot should be all that's needed.
(Though really all that's needed is fixing whatever broken manual process only works with RSA keys…)

My PEM file only had "BEGIN PRIVATE KEY" in it, not "BEGIN RSA PRIVATE KEY". When I regenerated using the --key-type RSA, Cerbot converted everything and all was well with ProScan.

~Dan

 

[belvdr]

DNS validation to acquire the keys occurs on port 80. A temporary port forward is all that's necessary to validate and acquire the keys. The incoming "https" requests to access the server and see the secure certificate don't use port 80.

DNS validation doesn’t use any ports on the endpoint. That is done via TXT records being added to the domain in question, so only the authoritative nameservers would be part of the validation. We do this all the time at work for various needs.

 

[belvdr]

I admit I did not verify that Comcast does _actually_ block port 80 and 443 for home IP addresses, but that's what the Interwebs' consensus appears to be.

~Dan

I despise when ISPs block any ports by default. There are online port checks you can use to verify.

 

[morrisr3nd]

The check driver message next to the port menu shows when you click on the serial port Auto Detect. and the serial port is non functional when the scanner is in Mass Storage mode.
In the Favorites editor, click on 'Scanner Read' A dialog should appear with the scanner showing.

I am at a loss on this one. It's got to be something with my computer.


With Scanner actually scanning:




While in USB Mass Storage Mode and AFTER pressing AUTODETECT: