web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

Error: Could not connect to the server. Please verify that

(0) ShareShare
ReportReport
Posted on by

Hi all

I have pulled and installed the latest BC docker image. 

VSIX: v6.1.350698

Base: 16.xxxxx

System: 16.xxxxx

Runtime: 6.0

Target: Cloud

I have installed the latest certificate and VSIX file, but I still get a connection error. We have mapped port 7049 to 8049.

Until now it has worked fine but after the latest install it stopped working. 

Anyone has an idea of what went wrong here? or if there is an internal error in the latest BC Docker that still keeps looking for 7049 instead of 8049?


[2020-10-14 10:40:09.18] Publishing AL application using launch configuration 'xxxxxxx'.
[2020-10-14 10:40:09.70] Targeting server 'https://xxxxxxxxx:8049' and server instance 'BC'.
[2020-10-14 10:40:09.86] Using user name and password authentication. User name used is: 'xxxx'.
[2020-10-14 10:40:09.89] Sending request to xxxxxxxxx:7049/.../metadata
[2020-10-14 10:40:11.08] Error: Could not connect to the server. Please verify that:
1. The server is started.
2. The development endpoint is enabled (DeveloperServicesEnabled server setting).
3. The service name matches the one specified in the URL.
4. The port number matches the one specified in the URL (DeveloperServicesPort server setting).
5. The protocol matches the one specified in the URL (DeveloperServicesSSLEnabled server setting), and that a trusted certificate is used in case of an SSL connection.
[2020-10-14 10:40:11.08] Error: An error occured while processing the request.
Request ID: b7f78ee4-842c-41f8-bf5a-447bb1e3b870
Session ID: c30047ea-5855-48fd-a74b-63eadf105ee2

If you are targeting a cloud instance, supply these IDs if contacting Microsoft support.

I have the same question (1)
  • Verified answer
    Community Member Profile Picture
    on at

    I found a solution. Add "Port" to Launch.json.

    {
        "version""0.2.0",
        "configurations": [
            {
                "name""xxxxxx",
                "type""al",
                "request""launch",
                "server""https://xxxxxxxx:8049",
                "serverInstance""BC",
                "authentication""UserPassword",
                "startupObjectType""Page",
                "schemaUpdateMode""ForceSync",
                "startupObjectId"123456,
                "breakOnError"true,
                "launchBrowser"true,
                "port": 8049

            }
        ]
    }
  • Marco Mels Profile Picture
    Microsoft Employee on at

    Thank you for sharing final solution, this does certainly help others.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 1,958 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,101 Super User 2026 Season 1

#3
Dhiren Nagar Profile Picture

Dhiren Nagar 959 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans