Error invalid number of arguments for encryption

**invalid number of arguments in "ssl_certificate_key" directive in   /etc/nginx/sites-enabled/default

sudo nano /etc/nginx/sites-enabled/default


upstream app {
# Path to Unicorn SOCK file, as defined previously
server unix:/home/zhall/zoulfia/shared/sockets/unicorn.sock fail_timeout=0;
}

server {
listen 80;
server_name moneytree.space www.moneytree.space " " 178.62.19.65;
rewrite ^/(.*) https://moneytree.space/ permanent;
}

# HTTPS server

server {
listen 443;
server_name moneytree.space www.moneytree.space " " 178.62.19.65;
root /home/zhall/zoulfia/public;


ssl on;
ssl_certificate /home/zhall/moneytree.space.chained.crt;

**ssl_certificate_key /home/zhall/ moneytree.space.key**

ssl_session_timeout 10m;

ssl_protocols SSLv3 TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers "HIGH:!aNULL:!MD5 or HIGH:!aNULL:!MD5:!3DES";
ssl_prefer_server_ciphers on;

location / {
try_files $uri $uri/ =404;
}
}

sudo service nginx restart

sudo nano /var/log/nginx/error.log, I get:

**invalid number of arguments in "ssl_certificate_key" directive in    /etc/nginx/sites-enabled/default

2 ответов

Expanding on the working answer from @mikhail-prigorodov:

The situation described by the OP arises when using the Nginx Docker container with Docker Compose. In the documentation, it reads:

Out-of-the-box, nginx doesn’t support environment variables inside most configuration blocks. But this image has a function, which will extract environment variables before nginx starts.

So, if you are using environment variables in your docker-compose.yml as part of a 12-Factor App design, you have to figure out how to get them into your Nginx config file properly.

The solution in the Nginx Docker documentation is to run envsubst on a template configuration file and send the output to the Nginx config file. The Dockerfile syntax, which is mentioned in this GitHub issue is:

CMD envsubst < /etc/nginx/templates/default.conf.template > /etc/nginx/conf.d/default.conf && exec nginx -g 'daemon off;'

But that solution runs into a problem if you have Nginx-defined variables AND environment variable placeholders in your configuration template. In the directory where I’m building my Nginx container (where my Dockerfile is), I have a templates directory with a file called default.conf.template, as directed in the documentation. The file contains Nginx variables and environment variables. For example:

proxy_set_header Host               $host;
proxy_set_header X-Real-IP          $remote_addr;

location /static {
    alias /usr/share/nginx/html/${STATIC_DIR};
}

The problem (I think) is that envsubst is looking for the «$» character that marks the start of the environment variables. In any case, you’ll find that after running envsubst successfully, each line in your new Nginx config file that has a Nginx-defined variable (leading «$») in the template gives an error when you try and start Nginx.

To solve this problem, use the syntax provided by @mikhail-prigorodov. Applied to my example:

CMD envsubst '$STATIC_DIR' < /etc/nginx/templates/default.conf.template > /etc/nginx/conf.d/default.conf && exec nginx -g 'daemon off;'

This was the solution that worked for me after hours of frustration.

@fevangelou I think there’s been some misunderstanding if I’m reading this regex correctly, it’s searching for an <IfModule ssl_module> block, inside every <VirtualHost example.com:443> block, but that isn’t how my certs are stored at all, I’ll just go ahead and paste a sanitized example of a live domain for you to better understand it, but I think this is definitely something with how EA4 or Apache 2.4 generates the httpd.conf, maybe even how AutoSSL interacts with it, I’m not sure, but all I know is that when I debug the https_vhosts file with print_r’s and echos, it returns 0 results even though it can read/parse the file.

<VirtualHost 1.2.3.4:8443>
    ServerName example.com
    ServerAlias mail.example.com www.example.com
    DocumentRoot /home/user/public_html
...
    SSLEngine on
    
    SSLCertificateFile /var/cpanel/ssl/installed/certs/example_com.crt
    SSLCertificateKeyFile /var/cpanel/ssl/installed/keys/example_com.key
    SSLCACertificateFile /var/cpanel/ssl/installed/cabundles/cPanel_Inc__example.cabundle
...
</VirtualHost>

any idea why the ssl_module block isn’t in there on any of them? I haven’t changed anything.

edit1: apparently its due to cpanels apache templates (/var/cpanel/templates/apache2_4), gonna see if I can update those.
edit2: I’ve deleted vhost.local and ssl_vhost.local files, and now its using the default ones which work correctly, I don’t understand how this happened and I’ve never edited or touched those files.

I’m building a simple fund raising smart contract and having problems deploying this through Remix. I’m wanting to set the «goal» and «minimum contribution» values (in wei) during the contract deployment and so have the following code:

pragma solidity ^0.5.0;

contract FundRaiser {
  // Initial storage variables
  uint256 public goal;
  uint256 public minimumContribution;
  address public owner;

  constructor(uint256 _goal, uint256 _minimumContribution) public {
    goal = _goal;
    minimumContribution = _minimumContribution;
    owner = msg.sender;
  }
}

This compiles fine in Remix and then I try to deploy and have the following prompt:

However, if I enter two large values here (1000000000000000000, 10000000000000000 — which equates to a goal of 1ETH with a minimum contribution of 0.01ETH) then I get the error:

creation of FundRaiser errored: Error encoding arguments: Error: invalid number value (arg="", coderType="uint256", value=10000000000000000, version=4.0.32)

If I then click the drop-down arrow next to the Deploy option it then shows the following:

Strangely Remix seems to have converted the first value into a string (surrounded by quotes) but not the second value. If I now update the values so that either both are strings or both are numbers and click «transact» then it deploys fine.

Is this an error on my part in using Remix or a bug??

ORA-00909: invalid number of arguments error occurs when there is a discrepancy between the number of arguments expected and the number of arguments provided when executing an Oracle function in a SQL query.In an Oracle function, if no arguments are given or if fewer than the required number of arguments are passed, the Oracle function will fail to execute. If the required number of arguments are not provided in the oracle function, an error message ORA-00909: invalid number of arguments is shown.

The Oracle function accepts a list of arguments as input, executes the function logic, and outputs a value. If an incorrect number of parameters is provided while invoking an Oracle function, the function logic cannot be executed. If no parameters or a less number of arguments are used, Oracle will display an error message ORA-00909: invalid number of arguments instead of executing the function.

If the number of argument values expected and the number of argument values passed in an oracle function do not match, the oracle function cannot execute without the argument value. The discrepancy is caused by a missed single quotes in the arguments, a line break between arguments, or some of the argument values being missed in the Oracle function. The error message ORA-00909: invalid number of arguments is displayed.

When the ORA-00909 error occurs

An error message is displayed if an Oracle function that takes one or more parameters is used in a SQL Statement and no or few arguments are used to invoke the function. Create a SQL statement that invokes an Oracle function. Without any arguments, use the Oracle function. Oracle will provide an error message indicating that the incorrect number of arguments were used in an Oracle function.

Problem

select sum() from emp;

Error

ORA-00909: invalid number of arguments
00909. 00000 -  "invalid number of arguments"
*Cause:    
*Action:
Error at Line: 40 Column: 8

Root Cause

Oracle functions can be executed with or without arguments. The Oracle function is defined by the number of arguments that must be passed to it when it is created. The number of arguments should be used in the SQL statements that call the Oracle function. Oracle functions could not be executed in the presence of the required number of arguments. The oracle error message will be displayed if any SQL Statement provides no arguments or the incorrect number of arguments in the oracle function.

Solution 1

Oracle functions can be defined either with or without parameters. The argument values are not required to be given to the function that does not require a value argument. If an Oracle function has one or more arguments, the argument values should be sent to the function when it is executed in a SQL query. If the number of arguments values given to the function is lesser than the expected number of arguments, an error message ORA-00909: invalid number of arguments will be shown.

Problem

select sum() from emp;

ORA-00909: invalid number of arguments
00909. 00000 -  "invalid number of arguments"

Solution

select sum(salary) from emp;

Solution 2

The number of necessary argument values in the Oracle nvl function is two in the example below. In the nvl() function, one of the parameter values is given. The function was not provided with an argument value for the other parameter. The number of arguments passed to the function and the number of parameters in the oracle function should both be the same.

When you execute the Oracle function in the sql query, the number of arguments, the datatype of the arguments, and the order of the arguments should all be the same. If there is a discrepancy in the list, an error message ORA-00909: invalid number of arguments will be displayed.

Problem

select nvl(name) from emp;

ORA-00909: invalid number of arguments
00909. 00000 -  "invalid number of arguments"

Solution

select nvl(name,'NA') from emp;