Exception while reading from stream postgresql как исправить

I am getting random error messages in my application log with the following stack trace. Most of the time everything is working well. I get about 10 errors and log messages like this a day in the p...

I am getting random error messages in my application log with the following stack trace. Most of the time everything is working well. I get about 10 errors and log messages like this a day in the production system. How do I figure out what is going on?

The issue

ERROR [18] 
 Npgsql.NpgsqlException (0x80004005): Exception while reading from stream ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
    at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
    --- End of inner exception stack trace ---
    at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
    at Npgsql.NpgsqlReadBuffer.<>c__DisplayClass31_0.<<Ensure>g__EnsureLong|0>d.MoveNext()
    at Npgsql.NpgsqlReadBuffer.<>c__DisplayClass31_0.<<Ensure>g__EnsureLong|0>d.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at Npgsql.NpgsqlConnector.<>c__DisplayClass161_0.<<ReadMessage>g__ReadMessageLong|0>d.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at Npgsql.NpgsqlConnector.<>c__DisplayClass161_0.<<ReadMessage>g__ReadMessageLong|0>d.MoveNext()
 --- End of stack trace from previous location where exception was thrown ---
    at Npgsql.NpgsqlDataReader.NextResult(Boolean async, Boolean isConsuming)
    at Npgsql.NpgsqlDataReader.NextResult()
    at Npgsql.NpgsqlCommand.ExecuteDbDataReader(CommandBehavior behavior, Boolean async, CancellationToken cancellationToken)
    at Npgsql.NpgsqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
    at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
    at Dapper.SqlMapper.ExecuteReaderWithFlagsFallback(IDbCommand cmd, Boolean wasClosed, CommandBehavior behavior) in C:projectsdapperDapperSqlMapper.cs:line 1051
    at Dapper.SqlMapper.QueryImpl[T](IDbConnection cnn, CommandDefinition command, Type effectiveType)+MoveNext() in C:projectsdapperDapperSqlMapper.cs:line 1079
    at System.Collections.Generic.List`1.AddEnumerable(IEnumerable`1 enumerable)
    at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
    at Dapper.SqlMapper.Query[T](IDbConnection cnn, String sql, Object param, IDbTransaction transaction, Boolean buffered, Nullable`1 commandTimeout, Nullable`1 commandType) in C:projectsdapperDapperSqlMapper.cs:line 721
    at Dapper.FastCrud.SqlStatements.GenericSqlStatements`1.BatchSelect(IDbConnection connection, AggregatedSqlStatementOptions`1 statementOptions) in D:a1sDapper.FastCrudSqlStatementsGenericSqlStatements.cs:line 297
    at XXX.Core.Data.SqlRepository`1.FirstOrDefault(String where, Object param, String order)
    at XXXXX.App.Worker.Tasks.XXX.Process() in C:DropboxdevSrcshopXXXTasksShopifyWebhookTask.cs:line 13
    at XXX.App.Worker.TaskBase`1.ProcessMessage(String message) in C:DropboxdevSrcshopXXXTaskBase.cs:line 30
    at Shop.Core.Common.Queue.BaseTaskProcessor`1.Process(QueueMessage message) in C:DropboxdevSrcshopXXXQueueBaseTaskProcessor.cs:line 38
Exception message:
Stack trace:

image

Npgsql version: 4.0.10
PostgreSQL version: 10.10
Operating system: Azure Windows Function + Azure Managed PostgresSql.

Содержание

  1. Npgsql.NpgsqlException (0x80004005): Exception while reading from stream #2962
  2. Comments
  3. Footer
  4. Exception while reading from stream #4532
  5. Comments
  6. Before submitting
  7. Steps to reproduce
  8. The issue
  9. Further technical details

Npgsql.NpgsqlException (0x80004005): Exception while reading from stream #2962

Npgsql.NpgsqlException (0x80004005): Exception while reading from stream
—> System.IO.EndOfStreamException: Attempted to read past the end of the stream.
at Npgsql.NpgsqlReadBuffer.<>c__DisplayClass34_0. d.MoveNext()
at Npgsql.NpgsqlReadBuffer.<>c__DisplayClass34_0. d.MoveNext()
— End of stack trace from previous location where exception was thrown —
at Npgsql.NpgsqlConnector.<>c__DisplayClass160_0. d.MoveNext()
— End of stack trace from previous location where exception was thrown —
at Npgsql.NpgsqlConnector.<>c__DisplayClass160_0. d.MoveNext()
— End of stack trace from previous location where exception was thrown —
at Npgsql.NpgsqlDataReader.NextResult(Boolean async, Boolean isConsuming)
at Npgsql.NpgsqlDataReader.NextResult()
at Npgsql.NpgsqlCommand.ExecuteReaderAsync(CommandBehavior behavior, Boolean async, CancellationToken cancellationToken)
at Npgsql.NpgsqlCommand.ExecuteNonQuery(Boolean async, CancellationToken cancellationToken)
at Npgsql.NpgsqlCommand.ExecuteNonQuery()
at LinqToDB.Data.DataConnection.ExecuteNonQuery()
at LinqToDB.Data.DataConnection.QueryRunner.ExecuteScalarImpl(DataConnection dataConnection, PreparedQuery preparedQuery)
at LinqToDB.Linq.QueryRunner.ScalarQuery(Query query, IDataContext dataContext, Expression expr, Object[] parameters)
at LinqToDB.Linq.QueryRunner.InsertWithIdentity`1.Query(IDataContext dataContext, T obj, String tableName, String databaseName, String schemaName)

The text was updated successfully, but these errors were encountered:

Thank you for reporting an issue, but there is not enough information to understand what’s happening. So please provide a minimal code example to reproduce the problem.

I get this error multiple times randomly while querying my database. I have used Linq2DB for db connection.

I tried by removing onresetonclose but no luck there.

Are you using pgbouncer as a connection pooler?

We have the same issue using pgbouncer instance between our .NET Core 3.1 app and the Postgres Server.

Could you send your select your are trying to execute?

Please see my issue if is not the same problem: #2966

Guys, there is nothing we can do with a simple exception message. Please check the PostgreSQL logs around the time of the exception, and if you suspect a real problem in Npgsql, then as @YohDeadfall wrote we need to see a runnable code sample that demonstrates the problem. Otherwise we can’t help you.

Am closing this as no code samples have been provided, and we can’t really do anything to investigate. If someone posts a code sample or at least some clear instructions on how to repro this, we can reopen and investigate.

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Exception while reading from stream #4532

Before submitting

This repo is for Npgsql ADO.NET issues only. My code is working fine while debugging. We are deploying the code in PCF.
It throws an exception while trying open the connection to PostgreSQL Server in Linux.

Steps to reproduce

The code is having issues while trying to open the connection.

The issue

Describe what is not working as expected.

Npgsql.NpgsqlException (0x80004005): Exception while reading from stream
—> System.TimeoutException: Timeout during reading attempt
Npgsql.Internal.NpgsqlReadBuffer.g__EnsureLong|41_0(NpgsqlReadBuffer buffer, Int32 count, Boolean async, Boolean readingNotifications)
Npgsql.Internal.NpgsqlConnector.RawOpen(SslMode sslMode, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken, Boolean isFirstAttempt)
Npgsql.Internal.NpgsqlConnector.g__OpenCore|191_1(NpgsqlConnector conn, SslMode sslMode, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken, Boolean isFirstAttempt)
Npgsql.Internal.NpgsqlConnector.Open(NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)
Npgsql.ConnectorPool.OpenNewConnector(NpgsqlConnection conn, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)
Npgsql.ConnectorPool.g__RentAsync|28_0(NpgsqlConnection conn, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)
Npgsql.NpgsqlConnection.g__OpenAsync|45_0(Boolean async, CancellationToken cancellationToken)

Further technical details

Npgsql version: 6.0.4
PostgreSQL version: 13.3
Operating system: Linux 8.x

Other details about my project setup:

The text was updated successfully, but these errors were encountered:

@arunsaho there are no details above — an exception message isn’t enough for us to help you. Please post a runnable code sample which triggers the issue, or at least provide more context.

string connString =
String.Format(
«Server=<0>;Username=<1>;Database=<2>;Port=<3>;Password=<4>;SSLMode=Prefer;Timeout=300;CommandTimeout = 300″,
Host,
User,
DBname,
Port,
Password);

Npgsql.NpgsqlException (0x80004005): Exception while reading from stream
—> System.TimeoutException: Timeout during reading attempt
Npgsql.Internal.NpgsqlReadBuffer.g__EnsureLong|41_0(NpgsqlReadBuffer buffer, Int32 count, Boolean async, Boolean readingNotifications)
Npgsql.Internal.NpgsqlConnector.RawOpen(SslMode sslMode, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken, Boolean isFirstAttempt)
Npgsql.Internal.NpgsqlConnector.g__OpenCore|191_1(NpgsqlConnector conn, SslMode sslMode, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken, Boolean isFirstAttempt)
Npgsql.Internal.NpgsqlConnector.Open(NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)
Npgsql.ConnectorPool.OpenNewConnector(NpgsqlConnection conn, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)
Npgsql.ConnectorPool.g__RentAsync|28_0(NpgsqlConnection conn, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)
Npgsql.NpgsqlConnection.g__OpenAsync|45_0(Boolean async, CancellationToken cancellationToken)
Npgsql.NpgsqlConnection.Open()

@arunsaho a network timeout during Open can occur for various reasons: you may have a firewall rule preventing the connection, there may be a misconfiguration, or if this happens intermittently, your network could be a bit flaky. In any case, this isn’t really related to Npgsql in any way — Npgsql simply establishes a standard TCP connection to the host and port you provide it.

If the error is reproducible and not intermittent, I’d recommend trying to connect to the same PostgreSQL (same host/port) from the same client machine where Npgsql is running, but from an external tool, e.g. the psql command-line tool. That would help isolate things.

Hello All — I’m getting a very similar error. We are using .net 6.0.7 Npgsql 6.0.5 AWS Arora Postgres 12.7 with RDS proxy. It is appearing in both our staging and prod environments. What is strange is it mainly appears in a simple query on a ver small table (prod

20 rows staging

5 rows) and the query is based on primary key. Our load can be high on prod at times but is extremely low in staging.

query
select * from public.companies where

What is more strange is that it is not a repeatable event. In other words, it only happens sometimes. We have been looking for the issue for about a month now. Any help would be appreciated. It is always this query . very strange not to see it on random queries if it was a connection issue. We have check the Postgres logs and see no errors of note.

Источник

This is the fifth day of my participation in the Gwen Challenge in November. Check out the details: The last Gwen Challenge in 2021 «.

The book continues…

5. Ghosts reappear

Since the test environment was not really consistent with the online environment, OM opened another AWS cloud database (PostgresQL) environment and allocated a domain name for test calls.

In order to be cautious, I used multithreading to test before delivering the product group, but found no problem, and transferred to the product group.

However, the product group found that the problem still existed after use.

This fucking BUG, it’s like a ghost. What’s going on?

I feel like I’m stuck in a loop.

6. Meditate

Start over, don’t give up, don’t give up!

To solve this problem, I looked through the cloud service’s database logs and found a useful clue.

Database LOG 2021-11-10 05:28:03 UTC:218.76.52.112(26828):[email protected]:[26849]:LOG: could not receive data from client: Connection reset by peer 2021-11-10 05:28:16 UTC:218.76.52.112(26346):[email protected]:[24160]:LOG: could not receive data from client: Connection reset by peer 2021-11-10 05:28:16 UTC:218.76.52.112(26504):[email protected]:[25374]:LOG: could not receive data from client: Connection reset by peer 2021-11-10 05:28:16 UTC:218.76.52.112(26361):[email protected]:[24280]:LOG: could not receive data from client: Connection reset by peerCopy the code

Connection reset by peer Connection reset by peer Reset by whom?

7 The connection is reset

The TCP connection is reset as follows:

  1. If the Socket on one end is closed (either actively closed or closed due to an abnormal exit) and the other end still sends data, the first packet sent raises the exception (Connect reset by peer).

The Socket is connected for 60 seconds by default. If there is no heartbeat interaction within 60 seconds, that is, data reading or writing, the connection is automatically closed.

  1. If one end exits without closing the Connection, the other end throws a Connection reset if it is reading data from the Connection.

Simply put, it is caused by read and write operations after the connection is disconnected.

Common reasons for situations:

  • The number of concurrent connections to the server exceeds its capacity, and the server closes some of them.

If the number of concurrent clients connected to the server does not exceed the carrying capacity of the server, the network traffic may be abnormal due to a virus or Trojan horse.

  • The client shuts down the connection while the server is still sending data to the client.
  • Firewall problems

If the network connection passes through a firewall, the firewall usually has a timeout mechanism. If the network connection does not transmit data for a long time, the TCP session is closed.

An exception will be generated if you try to read or write after the function is disabled. If the firewall is disabled and the problem is solved, you need to reconfigure the firewall or write programs to implement TCP long connections.

To implement TCP long connections, you need to define heartbeat protocols and send heartbeat protocols once in a while to maintain the connection.

8. Solve problems

Yes, THERE was no problem when I locally tested AWS services, while problems frequently occurred when the test environment connected to AWS servers. The biggest difference between us is the difference in network hardware channels.

It can be concluded that the database connection is cached in the connection pool, and when retrieved, the connection may have been closed by some proxy/firewall/router on the network, so there is an exception.

Npgsql.net version of PostgreSQL database connection strings and parameters

  1. Set ConnectionLifetime Set the maximum lifetime to 60s to prevent reuse
  2. Set the Keepalive heartbeat to prevent it from being reclaimed. Set to 30 s

I strongly pushed these two configurations to the product group. After half an hour, the product group feedback, the problem was solved!

9. Read the source code to find the root

We went to the ConnectorPool class, looked at its code, and found that it checks for disconnected status when it gets free links from the pool.

bool CheckIdleConnector([NotNullWhen(true)] NpgsqlConnector? connector)
        {
            if (connector is null)
                return false;

            

Of course, the comment also indicates that the disconnect check is valid if the KeepAlive parameter is set, and invalid if it is not. Yeah, without a heartbeat, it shouldn’t be able to check if the connection is down.

As you can see from the code, links that have timed out are also destroyed rather than returned to the client if the link lifecycle is set.

Moving on to the implementation code of NpgsqlConnector, you discover the secret of heartbeat checking.

_keepAliveTimer = new Timer(PerformKeepAlive, null, Timeout.Infinite, Timeout.Infinite);
Copy the code

If KeepAlive is set, then each link takes up 1 more thread.

The core code of the heartbeat check is as follows:

Log.Trace("Performing keepalive", Id);
 AttemptPostgresCancellation = false;
   var timeout = InternalCommandTimeout;
   WriteBuffer.Timeout = TimeSpan.FromSeconds(timeout);
   UserTimeout = timeout;
   WriteSync(async: false);
   Flush();
   SkipUntil(BackendMessageCode.ReadyForQuery);
   Log.Trace("Performed keepalive", Id);
Copy the code

A simple write SYNC takes care of the heartbeat maintenance and check.

From the above code, it makes sense to infer that if there is no heartbeat check, the status of links placed in the link pool is indeed unknown, and if they are disconnected by another gateway, the exception will be thrown if they are accessed again.

Yeah, so happy!

Nodule 10.

This troubleshooting, the total span of 2 weeks, a total of 2 times of fault analysis, each time about 2-3 days, it is not easy ah, you see to point support!

? have seen this, but also care about a thumbs-up?

? has been liked, but also care about a collection?

? are collected, but also care about a comment?

Aleksey писал(а):И втрой вариант, реализовать свои методы отмены или передачи конекшена через свой кастомный адаптер для PostgreSQL

Здравствуйте. Подключение к базе я смог получить, но я не могу «поймать» создание команд (IDbCommand). Я пробовал написать классы, унаследованные от StiOracleConnector / StiOracleAdapterService / StiOracleDatabase, и наблюдать за вызовом virtual-методов, но никто из них не занимается заполнением StiDataSource.

Суть проблемы: узнать какие запросы отправляет отчёт.

Заранее благодарен за помощь.

Вот, кстати, реализация получения текущего подключения (через событие DbConnectionBase.StateChange можно отлавливать момент открытия соединения). Вдруг кому-то пригодится.

Код: Выделить всё

public class MyDatabase : StiOracleDatabase
{
    protected override string DataAdapterType { get; } = typeof(MyAdapter).FullName;

    public MyDatabase()
        : this(string.Empty, string.Empty)
    {
    }

    public MyDatabase(string name, string connectionString)
        : base(name, connectionString)
    {
    }

    public MyDatabase(string name, string alias, string connectionString)
        : base(name, alias, connectionString)
    {
    }

    public MyDatabase(string name, string alias, string connectionString, bool promptUserNameAndpassword)
        : base(name, alias, connectionString, promptUserNameAndpassword)
    {
    }

    public MyDatabase(string name, string alias, string connectionString, bool promptUserNameAndpassword, string key)
        : base(name, alias, connectionString, promptUserNameAndpassword, key)
    {
    }

    public override StiSqlAdapterService GetDataAdapter() => new MyAdapter();
}

Адаптер:

Код: Выделить всё

public class MyAdapter : StiOracleAdapterService
{
    public override void CreateConnectionInDataStore(StiDictionary dictionary, StiSqlDatabase database)
    {
        base.CreateConnectionInDataStore(dictionary, database);

        // Подключения можно получить из DataStore:
        var connection = dictionary.DataStore[0].Data as OracleConnection;
    }
}

Добавление своей реализации:

Код: Выделить всё

StiReport.Dictionary.Databases.Add(new MyDatabase(name, connectionString));

Я получаю эту ошибку с перерывами в моем коде. Иногда это случается раз за разом. Иногда это происходит 1-из-10 раз. Я не делаю ничего уникального или специального в своем SQL, в отличие от другого плаката на StackOverflow, который выполнял команду COPY. Все, что я делаю, это SELECT.

Вот трассировка стека:

Exception while reading from stream
at Npgsql.ReadBuffer.Ensure(Int32 count, Boolean dontBreakOnTimeouts)
at Npgsql.NpgsqlConnector.DoReadMessage(DataRowLoadingMode  dataRowLoadingMode, Boolean isPrependedMessage)
at Npgsql.NpgsqlConnector.ReadMessageWithPrepended(DataRowLoadingMode dataRow LoadingMode) 
at Npgsql.NpgsqlConnector.ReadMessage(DataRowLoadingMode dataRowLoadingMode) 
at Npgsql.NpgsqlConnector.ReadExpecting[T]() 
at Npgsql.NpgsqlDataReader.NextResultInternal() 
at Npgsql.NpgsqlDataReader.NextResult() 
at Npgsql.NpgsqlCommand.Execute(CommandBehavior behavior) 
at Npgsql.NpgsqlCommand.ExecuteDbDataReaderInternal(CommandBehavior behavior) 
at Npgsql.NpgsqlCommand.ExecuteDbDataReader(CommandBehavior behavior) 
at System.Data.Common.DbCommand.ExecuteReader() 
at Npgsql.NpgsqlCommand.ExecuteReader() 
at JBetaFinder.Program.portfolioSimulation(String beginResult, String endResult) in c:UsersjDocumentsVisual Studio 2013ProjectsJBetaFinderJBetaFinderProgram.cs:line 571

Любые предложения о том, как избежать этой ошибки? Это проблема с Npgsql и postgres?

Вот мое SQL-выражение, которое представляется наиболее проблематичным:

select leg1.trade_date, sum(p.qty) as totalqty, max(gas.net_change)*10000 as avggaschange,  
            sum(((leg1.settlement_price - leg2.settlement_price) - (leg3.settlement_price - leg4.settlement_price))*qty*1000000) as spread_value_weight
            from quant_portfolio p
            inner join (select distinct trade_date, hub, product, strip, settlement_price, net_change
                            from public.icecleared_gas where contract = 'H') leg1
                            on p.leg1 = leg1.strip
            inner join (select distinct trade_date, hub, product, strip, settlement_price, net_change
                            from public.icecleared_gas where contract = 'H') leg2
                            on p.leg2 = leg2.strip and leg1.trade_date = leg2.trade_date                
            inner join (select distinct trade_date, hub, product, strip, settlement_price, net_change
                            from public.icecleared_gas where contract = 'H') leg3
                            on p.leg3 = leg3.strip and leg1.trade_date = leg3.trade_date                
            inner join (select distinct trade_date, hub, product, strip, settlement_price, net_change
                            from public.icecleared_gas where contract = 'H') leg4
                            on p.leg4 = leg4.strip and leg1.trade_date = leg4.trade_date  
            inner join (select distinct trade_date, hub, product, strip, contract, settlement_price, net_change
                            from public.icecleared_gas where contract = 'H') gas
                            on gas.strip = (select min(leg1) from quant_portfolio where commodity = 'NG') and gas.trade_date = leg1.trade_date                         
            where p.commodity = 'NG'
            AND (leg1.trade_date>='xxx' and leg1.trade_date<='yyy')
            group by leg1.trade_date
            order by leg1.trade_date

Я попытался переустановить SQL, чтобы вытащить sub-SELECTS и сделать их все соединения; не помогло, такая же ошибка.

Вот код С#, вызывающий Npgsql:

query = new NpgsqlCommand(getFullQuantPortBeta.ToString().Replace("xxx", beginResult.ToString()).Replace("yyy", endResult.ToString()), conn);
            dr = query.ExecuteReader();//code does not get past this line!
            beta = 0;
            while (dr.Read())
            {
                baselineData.Add(double.Parse(dr[2].ToString()));
                responseData.Add(double.Parse(dr[3].ToString()));
                if (baselineData.Count > 3)
                {
                    Tuple<double, double> result = MathNet.Numerics.LinearRegression.SimpleRegression.Fit(baselineData.ToArray(), responseData.ToArray());
                    beta = result.Item2 * BETA_MULT;
                    Console.WriteLine("WEIGHT BETA = " + beta);
                }
            }
            dr.Close();

posted on June 2nd, 2020

Good afternoon.
I am trying to connect the Flexmonster Data Server to my cloud database, and i find myself with the following error.
2020-06-02 13:25:05.6181|FATAL|Microsoft.AspNetCore.Hosting.Diagnostics|Application startup exception
2020-06-02 13:25:05.6618|FATAL|Flexmonster.DataServer.Program|Cannot connect to the database using «Server=xxxx;Port=xxxx;Uid=xxxx;Pwd=xxxx;Database=xxxx». Please check connection string. Details: Exception while reading from stream
My colleagues have investigated and the error is produced because the PostgreSQL database is protected with SSL certificates. We couldn’t find any information in your documentation regarding how to perform a connection to this kind of database. Would you please guide us through this process?

 Thanks for everything and kind regards.
Javier

7 answers

  1. Setting the Client Certificate connection string parameter.  
  2. Specifying the PGSSLCERT environment variable.
  3. Using ~/.postgresql/postgresql.crt (%APPDATA%postgresqlpostgresql.crt on Windows)

Good afternoon Vera.
I passed this information to our architects team, which are the ones in charge of deploying the Flexmonster server, and they haven’t been able to deploy it succesfully.
They tried to run it with ubuntu 20.04 and got the following error message: «No usable version of libssl was found …»
They told me to ask you which version/package of openssl is working/required, and if there is a quicker contact way they can address you directly their issues while deploying it.

 
Thanks for everything and best regards.
Javier

Hello Javier,

 
Thank you for the update.
Actually, we haven’t been reported about «No usable version of libssl was found» error previously, so it seems we need more time to investigate it. We will keep you updated.

 
However, after a brief research, it seems that a possible solution can be installing libopenssl1_0_0 package (more details are here https://stackoverflow.com/questions/53139591/dotnet-new-command-in-opensuse-causes-no-usable-version-of-the-libssl-was-fou ).

 
As for the communication channels, currently, our Forum is the most optimal way because all technical support team members have direct access to it and can respond quickly.

 
Please let us know if it helps.

 
Regards,
Ian

Hello, Javier, 

 
Thank you for giving us some time. 

 
Looking deeper, it seems the problem is caused by a conflict in the supported SSL library in .NET Core and the one used in Ubuntu.

Here are several links that may be of help:

  1. .NET Core 3.0 supports OpenSSL 1.1: https://github.com/dotnet/docs/issues/13475
  2. If you have LibreSSL instead of OpenSSL: https://github.com/dotnet/runtime/issues/24869
 

Please let us know if this helps to resolve the issue.
Looking forward to hearing from you.

 
Kind regards, 
Vera

Hello, Javier, 

 
How have you been? 

 
Our team would like to kindly take an interest in whether you found our previous response helpful. 
Did it work to configure the SSL connection?

 
Looking forward to your feedback.

 
Kind regards, 
Vera

Good afternoon Vera.

 
It took us a few days but using all your indications we were able to deploy it. Thanks for your feedback.

 
Best regards.
Javier

Hello, Javier, 

 
Thank you for your feedback. 

 
We are glad to hear that you managed to get everything working.
You are welcome to write to us if other questions arise.

Kind regards, 
Vera

Please login or Register to Submit Answer

Понравилась статья? Поделить с друзьями:
  • Except http error
  • Except error as error nameerror name error is not defined
  • Except connection error python
  • Excel число отформатировано как текст как исправить
  • Excel файл большого размера как исправить