Help running scan with FossID #8591
Replies: 8 comments 1 reply
-
This looks like a case of #8462. The work-around (or actually the fix) is to resolve the underlying access problem. |
Beta Was this translation helpful? Give feedback.
-
@sschuberth I am not so sure as the error happens now in I am a bit concerned that there are no output Could you please post your config-yml, without the sensitive data ? |
Beta Was this translation helpful? Give feedback.
-
I think the problem is that you have no naming pattern in the configuration. Try to add the following options to your config.yml:
|
Beta Was this translation helpful? Give feedback.
-
Hi @nnobelis , many thanks for the quick answer. This is an extract of my config now, after the changes:
And the error:
Maybe there is some info missing in the analyser result? |
Beta Was this translation helpful? Give feedback.
-
No I think it's an error in the communication format with FossID. Could you please parametrize the following curl request, run it and post us the response ?
|
Beta Was this translation helpful? Give feedback.
-
This is all I can get: I was trying with the web user/password but was always getting an authentication error. When I changed to the fossid database user/password, then it returns this error. When I check the nginx logs, nothing really useful appears there. FYI, I am using php 8.2 with fossid, not sure of this might be causing the problem. |
Beta Was this translation helpful? Give feedback.
-
Indeed, that was the issue. Everything works now, thank you for you help! |
Beta Was this translation helpful? Give feedback.
-
Glad to be of help. |
Beta Was this translation helpful? Give feedback.
-
Hi everyone,
I'm trying to run the scan with our FOSSID instance and I was able to configure the scan in the config-yml file, it looks like the connection works but I get the following error message. Can somebody help me to understand what's going on?
Many thanks!
Beta Was this translation helpful? Give feedback.
All reactions