[Artem Nesterko]

Artem Nesterko November 2, 2025 at 6:38 pm  

Thanks for the quick response! I only have two files: server.crt and server.key. I didn’t know about the CA bundle file.

Here’s my config:
“`yaml
server:
ssl: true
cert: certs/server.crt
key: certs/server.key
“`

I generated the certificates using:
“`bash
openssl req -x509 -newkey rsa:4096 -keyout server.key -out server.crt -days 365
“`

[Artem Nesterko]

Artem Nesterko November 2, 2025 at 6:37 pm  

Hi there,

Thank you for reaching out. SSL certificate validation errors are usually related to the certificate chain or file permissions. Let’s troubleshoot this step by step.

**First, let’s verify your certificate files:**

1. Make sure you have all three required files:
– Your certificate (server.crt)
– Private key (server.key)
– CA bundle/chain file (ca-bundle.crt)

2. Check file permissions – the private key should be readable only by the server process

Could you share your current `config.yml` SSL configuration section? Also, what command did you use to generate the certificates?

[Artem Nesterko]

Artem Nesterko November 2, 2025 at 6:36 pm  

AAAA

[Artem Nesterko]

Artem Nesterko November 2, 2025 at 6:35 pm  

AAAA

[Artem Nesterko]

Artem Nesterko November 2, 2025 at 6:34 pm  

Thanks for the quick response! I only have two files: server.crt and server.key. I didn’t know about the CA bundle file.

Here’s my config:
“`yaml
server:
ssl: true
cert: certs/server.crt
key: certs/server.key
“`

I generated the certificates using:
“`bash
openssl req -x509 -newkey rsa:4096 -keyout server.key -out server.crt -days 365
“`

[Artem Nesterko]

Artem Nesterko November 2, 2025 at 6:34 pm  

Hi there,

Thank you for reaching out. SSL certificate validation errors are usually related to the certificate chain or file permissions. Let’s troubleshoot this step by step.

**First, let’s verify your certificate files:**

1. Make sure you have all three required files:
– Your certificate (server.crt)
– Private key (server.key)
– CA bundle/chain file (ca-bundle.crt)

2. Check file permissions – the private key should be readable only by the server process

Could you share your current `config.yml` SSL configuration section? Also, what command did you use to generate the certificates?

[Artem Nesterko]

Artem Nesterko November 2, 2025 at 6:30 pm  

Thanks for the quick response! I only have two files: server.crt and server.key. I didn’t know about the CA bundle file.

Here’s my config:
“`yaml
server:
ssl: true
cert: certs/server.crt
key: certs/server.key
“`

I generated the certificates using:
“`bash
openssl req -x509 -newkey rsa:4096 -keyout server.key -out server.crt -days 365
“`

[Artem Nesterko]

Artem Nesterko November 2, 2025 at 6:30 pm  

Hi there,

Thank you for reaching out. SSL certificate validation errors are usually related to the certificate chain or file permissions. Let’s troubleshoot this step by step.

**First, let’s verify your certificate files:**

1. Make sure you have all three required files:
– Your certificate (server.crt)
– Private key (server.key)
– CA bundle/chain file (ca-bundle.crt)

2. Check file permissions – the private key should be readable only by the server process

Could you share your current `config.yml` SSL configuration section? Also, what command did you use to generate the certificates?

[Artem Nesterko]

Artem Nesterko November 2, 2025 at 6:22 pm  

Thanks for the quick response! I only have two files: server.crt and server.key. I didn’t know about the CA bundle file.

Here’s my config:
“`yaml
server:
ssl: true
cert: certs/server.crt
key: certs/server.key
“`

I generated the certificates using:
“`bash
openssl req -x509 -newkey rsa:4096 -keyout server.key -out server.crt -days 365
“`

[Artem Nesterko]

Artem Nesterko November 2, 2025 at 6:22 pm  

Hi there,

Thank you for reaching out. SSL certificate validation errors are usually related to the certificate chain or file permissions. Let’s troubleshoot this step by step.

**First, let’s verify your certificate files:**

1. Make sure you have all three required files:
– Your certificate (server.crt)
– Private key (server.key)
– CA bundle/chain file (ca-bundle.crt)

2. Check file permissions – the private key should be readable only by the server process

Could you share your current `config.yml` SSL configuration section? Also, what command did you use to generate the certificates?

[Artem Nesterko]

Artem Nesterko November 2, 2025 at 6:15 pm  

Thanks for the quick response! I only have two files: server.crt and server.key. I didn’t know about the CA bundle file.

Here’s my config:
“`yaml
server:
ssl: true
cert: certs/server.crt
key: certs/server.key
“`

I generated the certificates using:
“`bash
openssl req -x509 -newkey rsa:4096 -keyout server.key -out server.crt -days 365
“`

[Artem Nesterko]

Artem Nesterko November 2, 2025 at 6:15 pm  

Hi there,

Thank you for reaching out. SSL certificate validation errors are usually related to the certificate chain or file permissions. Let’s troubleshoot this step by step.

**First, let’s verify your certificate files:**

1. Make sure you have all three required files:
– Your certificate (server.crt)
– Private key (server.key)
– CA bundle/chain file (ca-bundle.crt)

2. Check file permissions – the private key should be readable only by the server process

Could you share your current `config.yml` SSL configuration section? Also, what command did you use to generate the certificates?

[Artem Nesterko]

Artem Nesterko November 2, 2025 at 6:02 pm  

Perfect! That’s the issue. You’re using a self-signed certificate, which is fine for testing, but you’re missing the CA bundle configuration.

For self-signed certificates, you have two options:

**Option 1: Add the certificate to your trusted store (recommended for testing)**
– This makes your system trust the self-signed cert
– No config changes needed

**Option 2: Disable certificate verification (development only)**
“`yaml
server:
ssl: true
cert: certs/server.crt
key: certs/server.key
verify_cert: false # Add this line
“`

**For production, you should use a proper SSL certificate from a Certificate Authority like Let’s Encrypt.**

Would you like instructions on getting a free Let’s Encrypt certificate?

[Artem Nesterko]

Artem Nesterko November 2, 2025 at 6:01 pm  

Thanks for the quick response! I only have two files: server.crt and server.key. I didn’t know about the CA bundle file.

Here’s my config:
“`yaml
server:
ssl: true
cert: certs/server.crt
key: certs/server.key
“`

I generated the certificates using:
“`bash
openssl req -x509 -newkey rsa:4096 -keyout server.key -out server.crt -days 365
“`

[Artem Nesterko]

Artem Nesterko November 2, 2025 at 6:01 pm  

Hi there,

Thank you for reaching out. SSL certificate validation errors are usually related to the certificate chain or file permissions. Let’s troubleshoot this step by step.

**First, let’s verify your certificate files:**

1. Make sure you have all three required files:
– Your certificate (server.crt)
– Private key (server.key)
– CA bundle/chain file (ca-bundle.crt)

2. Check file permissions – the private key should be readable only by the server process

Could you share your current `config.yml` SSL configuration section? Also, what command did you use to generate the certificates?

[Artem Nesterko]

Artem Nesterko January 9, 2025 at 5:02 am  

I suspect it is not working due to the installation on Windows.

I need some time to investigate.

Will you be available for a meeting next week?

I do not know the day yet as I need to prepare for the investigation.

[Artem Nesterko]

Artem Nesterko January 5, 2025 at 10:35 pm  

Yes, the latest version per our changelog.

Please apply it to get the latest features.

[Artem Nesterko]

Artem Nesterko January 4, 2025 at 12:38 am  

Please let me know if you want the excel output of Blitz Report to be saved on the application server?

If yes, please use Additional Out. Directory on APPS Server runtime option.

Additional Out. Filename runtime option can be used to customize that additional output file name.

[Artem Nesterko]

Artem Nesterko January 3, 2025 at 9:17 pm  

This is possible in your current version 3.2.4.

Please create a directory on the apps server. E.g. /tmp/output

Populate ‘Add. Out. Dir. APPS Node’ runtime option with that directory before running the report

Find the output of this report in that directory.

Tokens are only for additional flexibility in naming directories and output files. They are not mandatory to use.

Please test and let me know if it works for you.

[Artem Nesterko]

Artem Nesterko January 1, 2025 at 6:16 pm  

It looks like you are using an older version of Blitz.

You can either upgrade to the latest version or use the current version without tokens and ‘Add. Out. Filename Pattern’ instead of the Additional Out FIle Name.

Please let me know what you think?

[Artem Nesterko]

Artem Nesterko January 1, 2025 at 6:47 am  

Here is the link to the upgrade instructions.

Basically you just need to download the latest Blitz and run install.sh in MKS bash, it will upgrade everything automatically.

[Artem Nesterko]

Artem Nesterko January 1, 2025 at 12:49 am  

Yes Blitz Report is supported with EBS 12.2.12 on Linux.

We always test Bltiz Report with the latest EBS releases on Linux.

To prepare you can create a custom XXEN application as per our installation guide.

Apart from that the installation should be quick and straightforward.

[Artem Nesterko]

Artem Nesterko December 30, 2024 at 11:58 pm  

Could you please send me the concurrent request log?

[Artem Nesterko]

Artem Nesterko December 30, 2024 at 8:17 pm  

The LOV for the DB Node gets the data from the dba_directories.

So you can create a new directory in the database, so it is displayed in the LOV as follows.

[Artem Nesterko]

Artem Nesterko December 30, 2024 at 3:48 am  

Please perform following tests:

1) In addition to ‘Add. Out. Dir APPS Node’

Set ‘Add. Out. Filename Pattern’ to any value from the LOV, e.g. _’YYYYMMDD’

Run the report.

Check if the output was copied to the folder.

2) If the folder is still empty.

Set ‘Add. Out. Dir APPS Node’ to ‘Z:\invalid_directory’.

Run the report.

Send me the request log.

I want to understand if Blitz tries to copy the file at all.

If the disk/directory is invalid, it should produce an error in the log.

Thank you.

[Artem Nesterko]

Artem Nesterko December 29, 2024 at 7:16 pm  

To enable it at the report level, please go to the Setup screen->Options and set the “Add. Out. Dir. DB Node” option.

The screen may differ a bit in your version.

This way the associated runtime option is going to inherit the report level value automatically.

Attachments:

1. 

   1-8.png
   

[Artem Nesterko]

Artem Nesterko December 29, 2024 at 1:55 am  

This is not an error in the report. These 2 vendors each have 2 vendor sites defined as attached.

Attachments:

1. 

   1-15.png
   

[Artem Nesterko]

Artem Nesterko December 29, 2024 at 1:39 am  

The supplier is derived from the sourcing rules for the specified Assignment Set defined in the EBS instance.

Attachments:

1. 

   1-17.png
   

[Artem Nesterko]

Artem Nesterko December 28, 2024 at 12:36 pm  

Hi,

This is due to the automated column translation feature, which would not just convert an UPPER_CASE_COLUMN to a more readable Upper Case Column. This feature also translates some of the most common column names to local language, in case a user is logged on with a different language than US.

You can disable this translation with the options checkbox.

Alternatively, if you do not require the underscore, you can do the following:

select

aps.vendor_name “VENDOR NAME”

from

ap_suppliers aps

Or, if you don’t mind having an extra space in the excel cell:

select

aps.vendor_name “VENDOR_NAME ”

from

ap_suppliers aps

Let me know if this works for your requirement.

Attachments:

1. 

   1-5.png
   

[Artem Nesterko]

Artem Nesterko December 28, 2024 at 2:36 am  

Yes, Blitz Report 3.2.6 is supported on r12.2.11 and Linux.

[Author]

Replies