Error critical error could not connect to server - Исправление ошибок и поиск оптимальных решений проблем

Below you find a step by step guide, if you prefer you can watch our How to Resolve the Critical Error “Could not Connect to Server” video tutorial.

This error usually means that the login details or method set for a remote connection are incorrect.

Check:

The user ID and password that you entered. Note that for many website hosting providers, the user ID and password that you use to login to the website itself will be different to the user ID and password that you need for file transfer connections. Look for FTP or SFTP or SSH connection details in the information provided by the hosting provider.
The type of login configured for this site. In the Site Manager, select the connection
and check the Logon Type drop down list. Most servers will refuse Anonymous automatically.

Status: Connection attempt failed with "ECONNREFUSED - Connection refused by server" message

If the connection is failing with the status message above, there might be a local network configuration issue. FileZilla/FileZilla Pro has a network configuration wizard that can find common issues in network and router settings.

To diagnose:

In the main menu click on Edit > Network configuration wizard….
Click on Next
Enter details as requested – if you’re unsure, you can usually use the default configuration settings and just click Next at each screen.

Once FileZilla/FileZilla Pro has gathered all the configuration information it needs, it will perform a test connection on a test server run by the FileZilla team. If the test connection works with no errors, then the problem probably exists on the remote site that you’re trying to connect to.

Another possible cause is that the connection is being blocked by a firewall. If you have a local firewall or an antivirus, try to disable it. If that works you may need to add an exception to the firewall configuration to grant FileZilla Pro permanent access to the network.

If you are in a corporate network, you may need to ask the network administrator to open specific FTP ports.
Most FTP servers use port 21, SFTP servers use port 22 and FTPS (implicit mode) use port 990 by default.

The video tutorial below shows how to resolve the critical error “Could not Connect to Server”

Video tutorial: How to Fix Connection Error

Источник

Moderator: Project members

talk2jo: 500 Command not understood; Posts: 3; Joined: 2013-01-29 02:03

Critical Error Could not connect to server

Post

by talk2jo » 2013-01-29 02:08

Trying to upload a website for a client. The following error occurs. Can someone advise what it means and what I should do? Many thanks

Status: Resolving address of warraguldowntowner.com.au
Status: Connecting to 203.12.234.194:21…
Status: Connection established, waiting for welcome message…
Response: 220 Microsoft FTP Service
Command: USER warraguldowntownerco
Response: 331 Password required for warraguldowntownerco.
Command: PASS ***********
Response: 530 User warraguldowntownerco cannot log in.
Error: Critical error
Error: Could not connect to server

boco: Contributor; Posts: 26451; Joined: 2006-05-01 03:28; Location: Germany

Re: Critical Error Could not connect to server

Post

by boco » 2013-01-29 03:32

Either the login data for the server is wrong or there are other problems on the server side (like user database error or a suspended account).

Please double-check your credentials and contact the server administrator, should the problems persist.

### BEGIN SIGNATURE BLOCK ###
No support requests per PM! You will NOT get any reply!!!
FTP connection problems? Do yourself a favor and read Network Configuration.
FileZilla connection test: https://filezilla-project.org/conntest.php
### END SIGNATURE BLOCK ###

talk2jo: 500 Command not understood; Posts: 3; Joined: 2013-01-29 02:03

Re: Critical Error Could not connect to server

Post

by talk2jo » 2013-01-29 05:01

thanks so much for that, have connected now with new password.

What I normally do now is just drag my files into Public HTML folder, it appears this is not there or renamed.

Can you tell me if I drag files into the top level folder (warraguldowntownerco) everything will be ok? See attached.

I just don’t want to mess this up — first time I’m uploading for client who already has a live website.

Many thanks

Attachments

: Screen shot 2013-01-29 at 3.56.36 PM.png (45.32 KiB) Viewed 173398 times

boco: Contributor; Posts: 26451; Joined: 2006-05-01 03:28; Location: Germany

Re: Critical Error Could not connect to server

Post

by boco » 2013-01-29 05:28

Since it varies from hoster to hoster, or even from website to website, I cannot answer that, unfortunately. Just check if there is an existing index.html file.

leakie: 500 Command not understood; Posts: 3; Joined: 2013-02-07 11:36; First name: lee; Last name: drury

Re: Critical Error Could not connect to server

Post

by leakie » 2013-02-07 12:12

im getting :

Command: USER user1295
Response: 331 Password required for user1295
Command: PASS ********
Response: 530 Login incorrect.
Error: Critical error
Error: Could not connect to server

worked everytime up to this morning .. ive even extended my ftp for another month incase that had run out but still getting this ?

thanks

leakie: 500 Command not understood; Posts: 3; Joined: 2013-02-07 11:36; First name: lee; Last name: drury

Re: Critical Error Could not connect to server

Post

by leakie » 2013-02-07 12:16

ive tried configuration wizard and i get this :

Response: 331 Give any password.
PASS 3.6.0.2
Response: 230 logged on.
Checking for correct external IP address
IP 192.168.1.132 bjc-bgi-b-bdc
Response: 510 Mismatch. Your IP is 188.221.215.46, bii-ccb-cbf-eg
Wrong external IP address
Connection closed

confused

leakie: 500 Command not understood; Posts: 3; Joined: 2013-02-07 11:36; First name: lee; Last name: drury

Re: Critical Error Could not connect to server

Post

by leakie » 2013-02-07 13:04

ok thankyou

CaptainBoc: 421 Kicked by Administrator; Posts: 1; Joined: 2013-08-05 21:21

Re: Critical Error Could not connect to server

#10

Post

by CaptainBoc » 2013-08-05 21:22

boco wrote:Contact your hoster, server issue.

Just been having the same problem (with hostgator), sent them a message and they sorted it out for me
Thanks for the help!!

keelmac: 500 Command not understood; Posts: 2; Joined: 2015-03-10 20:26; First name: Carol; Last name: K

Re: Critical Error Could not connect to server

#11

Post

by keelmac » 2015-03-10 20:29

Status: Connection established, waiting for welcome message…
Status: Initializing TLS…
Status: Verifying certificate…
Status: TLS connection established.
Command: USER mysticrun
Response: 331 User mysticrun OK. Password required
Command: PASS ***********
Response: 530 Login authentication failed
Error: Critical error: Could not connect to server

I have tried the password several time and even used 2 different ftp and neither is working please help

boco: Contributor; Posts: 26451; Joined: 2006-05-01 03:28; Location: Germany

Re: Critical Error Could not connect to server

#12

Post

by boco » 2015-03-10 21:52

1. Please don’t cross-post into multiple topics.

2. Your username and/or password are invalid and do not work for the server you’re trying to connect to. Check for syntax errors or leading/trailing blanks. Note that login data might be case sensitive. If that still won’t resolve it you need to contact server support.

keelmac: 500 Command not understood; Posts: 2; Joined: 2015-03-10 20:26; First name: Carol; Last name: K

Re: Critical Error Could not connect to server

#13

Post

by keelmac » 2015-03-11 00:26

Sorry i just noticed that no had posted in this on for a year so i went somewhere that was active nd i just changed the password and im sti getting the error

boco: Contributor; Posts: 26451; Joined: 2006-05-01 03:28; Location: Germany

Re: Critical Error Could not connect to server

#14

Post

by boco » 2015-03-11 12:14

1. Especially when copy-pasting, very often a blank character is copied along with the rest. Although invisible and unwanted, it is regarded as past of the username/password. If the password isn’t too complex, try typing it out.
2. When you change passwords with your hoster, be sure to change the FTP password. Usually it is not the same as website access. With some hoster you have to enable FTP access first.
3. After an FTP password change, allow the hoster some time for making the change. Login data change might propagate with a delay.
4. Maybe a silly point, but: Make sure you’re connecting to the correct server. We had cases of that, before.

123tc: 500 Command not understood; Posts: 2; Joined: 2015-04-20 07:10; First name: TC; Last name: 123; Contact:

Re: Critical Error Could not connect to server

#15

Post

by 123tc » 2015-04-20 07:23

Error: Critical Error Could not connect to server

Status: Resolving address of trochoithoitrang.net
Status: Connecting to 221.132.35.236:21…
Status: Connection established, waiting for welcome message…
Response: 220 ProFTPD 1.3.3c Server ready.
Command: USER ********
Response: 331 Password required for trocho
Command: PASS ********************************************
Response: 530 Login incorrect.
Error: Critical error: Could not connect to server

Accessible via DirectAdmin user and password sign into normal FTP. But when the Japanese version, the new version of Filezilla go this error occur with all my FTP account.

Install + update on Mac not works?

Pls help me

Last edited by 123tc on 2015-04-20 07:33, edited 1 time in total.

Источник

Is FileZilla showing Critical error: Could not connect to the server? We can help you fix it.

Usually, FTP clients like FileZilla shows a connection error due to the incorrect protocol or incorrect login credentials.

Here at Bobcares, we often get requests from our customers to fix FileZilla errors as part of our Server Management Services.

Today, let’s see how our Support Engineers fix this error for our customers.

What is the difference between FTP and SFTP?

Before reading more about the error, let’s get an idea of FTP and SFTP.

The FTP and SFTP are two different protocols used for file transfer.

FTP transfer the password and data in the plain text format whereas, SFTP encrypts the data before sending it to another host.

FTP doesn’t provide a secure channel to transfer files between hosts whereas SFTP offers a secure channel for transferring files between the hosts. Thus, SFTP is found to be more secure than the FTP protocol.

How to fix Critical error could not connect to Server?

At Bobcares, where we have more than a decade of expertise in managing servers, we see many customers face this problem.

Now, let’s see how our Support Engineers fix the error for our customer in simple steps.

1. Incorrect Protocol

The customer got the below error when he tried to establish an FTP connection with an SFTP server.

Error: Cannot establish FTP connection to an SFTP server. Please select proper protocol.
Error: Critical error: Could not connect to server

On checking, we found that the protocol is incorrect. For the proper connection, the protocol should be SFTP and not FTP.

We fixed the error easily by enabling the SFTP protocol instead of FTP. Both the SFTP and FTP are different file transfer protocols and the main difference with the protocols is associated with security.

We asked customer to fix the error using these simple steps.

1. Initially, open FileZilla.

2. Then go to File and click the Site Manager option.

3. In the Site Manager, go in the General tab and select SFTP in Protocol.

Finally, choose Logon Type as Normal and provide a valid username and Password.

Also, provide the Host details and Port number as 22.

This fixes the Critical error: could not connect to Server in FileZilla during establishing an FTP connection to an SFTP server.

2. Incorrect login credentials

Very often, some customers may get the below error in FileZilla.

Response: 530 Login authentication failed
Error: Critical error: Could not connect to server

This error occurs when users enter an incorrect username/password or host. So we advise our customers to check the username and password are correct.

[Need any assistance with FileZilla Errors – We can help you fix it]

Conclusion

In short, Critical error: Could not connect to Server in FileZilla happens due to incorrect protocol or wrong login details. Also, we saw how our Support Engineers helped our customer to resolve the connection error in FileZilla.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Источник

If you try to connect to a SFTP server using FileZilla, you may see a Critical error: Could not connect to server. Here’s why you see this error and how to fix it.

The other day I had to connect to my web server. I use FileZilla for connecting to FTP servers. FileZilla is a free and open source GUI software that allows you to connect to a FTP server in Linux.

When I entered the hostname and password and tried to connect to the FTP server, it gave me the following error:

Error: Cannot establish FTP connection to an SFTP server. Please select proper protocol.
Error: Critical error: Could not connect to server

FileZilla Cannot establish FTP connection to an SFTP server

Fixing ‘Critical error: Could not connect to server’ in Linux

By reading the error message itself made me realize my mistake. I was trying to establish an FTP connection with an SFTP server. You see, I had SFTP setup on the Linux server. Clearly, I was not using the correct protocol which should have been SFTP and not FTP.

As you can see in the picture above, FileZilla defaults to FTP protocol.

Solution for “Cannot establish FTP connection to an SFTP server”

Solution is simple. Use SFTP protocol instead of FTP. The one problem you might face is to know how to change the protocol to SFTP. This is where I am going to help you.

In FileZilla menu, go to File->Site Manager.

In the Site Manager, go in General tab and select SFTP in Protocol. Also fill in the host server, port number, user password etc.

I hope you can handle things from here onward.

I hope this quick tutorial helped you to fix “Cannot establish FTP connection to an SFTP server. Please select proper protocol.” problem. If you have questions or suggestion, do let me know. If this article helped you fix the problem, I won’t mind a simple ‘thanks’ comment

In related articles, you can read this post to know how to set up FTP server in Linux.

Источник

Is FileZilla showing a Critical Error: Could not interface with the specialist? We can help you with fixing it.

FileZilla critical error: could not connect to the server, Normally, FTP clients like FileZilla show a connection bungle due to the mistaken show or incorrect login confirmations.

Here at ARZHOST, we consistently get requests from our customers to fix the FileZilla error as an element of our Server Management Services.

This error normally infers that the login shades or method set for a far-off connection aren’t right.

Check:

The customer ID and mystery state that you entered. Note that for a few, sites working with providers, the customer ID and mystery state that you use to login to the genuine site will be different from the customer ID and mystery key that you need for report move connections. Quest for FTP or SFTP or SSH connection hints in the information given by the working with the provider.
The kind of login intended for this site. In the Site Manager, select the connection
likewise, and check the Logon Type drop-down list. Most specialists will deny Anonymous normally.

Status: Connection attempt failed with "ECONNREFUSED - Connection denied by specialist" message

FileZilla critical error: could not connect to the server, If the connection is failing with the status message above, there might be a close-by association configuration issue. FileZilla/FileZilla Pro has an association arrangement expert that can find ordinary issues in association and switch settings.

To analyze:

In the standard menu click on Edit > Network arrangement wizard….
Snap-on Next
Enter nuances as a reference if you’re dubious, you can commonly use the default course of action settings and essentially click Next at each screen.

At the point when FileZilla/FileZilla Pro has gathered all the plan information it needs, it will play out a test relationship on a test specialist run by the FileZilla group. FileZilla critical error: could not connect to the server, Expecting the test connection works with no error, the issue exists on the far-off site that you’re trying to interface with.

Another possible explanation is that the connection is being impeded by a firewall. If you have a local firewall or antivirus, effort to impede it. If that works you may need to add an exceptional case for the firewall game plan to permit FileZilla Pro durable permission to the association.

FileZilla critical error: could not connect to the server, If you are in a corporate association, you may need to demand that the association head open unequivocal FTP ports.

Features of FileZilla critical error

FileZilla’s features include a content comparison between the local and remote directories.
A FileZilla shows the status of transferred files and those in the queue.
The site manager creates and stores a list of FTP servers and their associated data.
Allows file and folder adjustments and supports drag and drop.

Using FileZilla to establish a server connection and transfer files

From the menu bar, choose FileZilla, which has been installed.
Select Site Manager from the Files menu.
In the box that appears, select New Site.
Select In the Protocol box, choose SFTP – SSH File Transfer Protocol.
In the Host box, type the server address you want to connect to, and in the Port box, type 22.
Select Connect after entering the user name that was allocated to you in the User box.
If you trust the host, you can go to the next stage by selecting Always trust this host and clicking OK.
To connect, enter the password and then click OK.

A box will show when FileZilla is launched. Your local computer is on the left, and the remote site is on the right. You can now transfer files by dragging and dropping them or copying them. If you have any problems installing FileZilla. Connecting to the server, or transferring files, contact your server administrators for assistance. Arzhost is a high-end server management firm that provides top-notch server assistance to businesses of all sizes.

After you’ve completed your successful installation. You can run into some technical difficulties connecting to FTP or SFTP. In most cases, these problems are caused by erroneous login credentials or incorrect remote connection protocols. Let’s look at some other reasons why critical errors occur. FileZilla was unable to connect to the server.

What is the qualification of FTP and SFTP?

Before examining more about the Error, we should get some answers concerning FTP and SFTP. The FTP and SFTP are two particular shows use for archive move.

FileZilla critical error: could not connect to a server, FTP moves the mysterious key and data in the plain message plan while SFTP encodes the data before sending it to another host.

FTP doesn’t give a protected channel to move records between has while SFTP offers a secured channel for moving archives between the hosts. Likewise, SFTP is seen to be more secure than the FTP show.

How do fix Critical errors that couldn’t interface with the Server?

At ARZHOST, where we have domination in regulating workers, we see various customers manage this issue.

By and by, what about we see how FileZilla critical error: could not connect to the server, our Support Engineers fix the error for our customer in clear advances.

1. Mistaken Protocol

The customer got the underneath error when he endeavored to set up an FTP relationship with an SFTP specialist.

Error: Cannot develop FTP relationship with an SFTP specialist. In case it's not all that much difficulty, select the proper show.

Error: Critical slip-up: Could not connect with worker

On checking, we found that the show isn’t right. FileZilla critical error: could not connect to a server, For the proper connection, the show should be SFTP and not FTP.

We fixed the error successfully by engaging the SFTP show instead of FTP. Both the SFTP and FTP are unmistakable report move shows and the essential differentiation between the shows is connect with security.

FileZilla critical error: could not connect to a server, we mentioned that the customer fixes the slip-up using these direct advances:

From the start, open FileZilla.
Then go to File and tap the Site Manager decision.
In the Site Manager, go to the General tab and select SFTP in Protocol.

Finally, pick Logon Type as Normal and give a genuine username and Password.

This fixes the Critical error: couldn’t interface with Server in FileZilla during developing an FTP relationship with an SFTP worker.

2. Incorrect login statements

FileZilla critical error: could not connect to the server, as often as possible, a couple of customers may get the under screw up in FileZilla.

Response: 530 Login approval failed

Error: Critical misstep: Could not connect with a specialist

This error happens when customers enter an off-base username/secret expression or host. So we urge our customers to check the username and mystery express are correct.

Conclusion

Along these lines, Critical Error: Could not connect with Server in FileZilla happens due to off base show or wrong login hints. FileZilla critical error: could not connect to the server, Also, we saw how our Support Engineers helped our customer with settling the connection botch in FileZilla.

Related Articles

What Is Incoming Mail Server Hostname

What is DOS Attack ACK Scan?

Telnet Connect to Address Connection Refused, how to fix it!

Источник

If you have problems connecting to your FTP account using FileZilla, check out the information below to help you solve the problem.

Response: 530 Login authentication failed

Response: 530 Login authentication failed
Error: Critical error
Error:  Could not connect to server

If you see this error message when trying to connect it means that you entered an incorrect username/password or host. If you don’t remember your login details, please follow the steps in this tutorial to reset it.

Your domain name must point to your hosting account. This happens by pointing your domain name’s DNS A record to your hosting account’s IP address.

Response: 421 Sorry, cleartext sessions are not accepted on this server

Response:    421 Sorry, cleartext sessions are not accepted on this server.
Error:    Could not connect to server

If you see this message, please check and make sure that FileZilla is set to use the following details:

Protocol: FTP protocol
Encryption: Require FTP over explicit TLS/SSL
LogonType : Normal

Filezilla timeout after 20 seconds of inactivity

Open Site manager
Click on “New site” button
You need to change the Encryption to “Only use plain FTP (insecure)” and Logon type to Normal
Enter host address, user name, and password and click “Connect”

Response: 500 unrecognized command

Response: 500 unrecognized command
Error:  Could not connect to server

This error can be caused by an incorrect port setting, please make sure you are using the correct port 21.

Response: 331 User savsuq2b1 OK. Password required

Error: Connetion timed out
Error: Could not connect to server

If you see this error you’ll first need to make sure that you’re using the correct login information. If they are all correct, you’ll need to check for Firewalls or Antivirus installed on your computer, try disabling them and test the connection again.

Response: Connection timed out (Failed to retrieve directory listing)

Error: Connection timed out after 10 seconds of inactivity
Error: Failed to retrieve directory listing

There could be a Firewalls or Antivirus problem, which might be blocking the transfer, try disabling them and test the connection again.

By default, FileZilla is defined to close the transfer of files if the file transfer takes more than a fixed amount of time, so if the disabling the Firewall doesn’t fix the problem you should try disabling the timeout settings.To disable the timeout select Edit -> Settings -> Connections -> Change Timeout to a higher value.

Connection attempt failed with “EAI_NONAME

Full error: Connection attempt failed with “EAI_NONAME – Neither nodename nor servname provided, or not known”.

If you see this error, this means that the issue is related to Name resolution error. The “Host” you are using is not correct, or your domain may not be pointed to our DNS. Check for spelling mistakes or try using the server’s IP address.

If you enjoyed this tutorial, then you’ll love our support! All ChemiCloud’s hosting plans include 24/7 support from our amazing support team. Check out our web hosting plans and have your website migrated today!

Источник

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

Closed

jquilliam opened this issue

Apr 26, 2016

· 45 comments

Comments

I have installed SP and the first time a user opens it, it works. but if you close it or log in as a different user you get this error «Critical server error — could not connect to server!». if you restart it it work for the first boot up, but then after that you cant open it again.

I am running windows 8.1/ server 2012

Below you will see the error report.

Sonic Pi Boot Error Report

System Information

Sonic Pi version: 2.10.0
OS: Assuming Linux

GUI Log

C:Usersjquilliam2.sonic-piloggui.log

Permissions error: unable to access log

Server Errors

C:Usersjquilliam2.sonic-pilogserver-errors.log

Permissions error: unable to access log

Server Output

C:Usersjquilliam2.sonic-pilogserver-output.log

Permissions error: unable to access log

Scsynth Output

C:Usersjquilliam2.sonic-pilogscsynth.log

Permissions error: unable to access log

Wow, that’s very odd — it seems to think you’re running under Linux — something is clearly broken here. Out of interest, do you have a .sonic-pi directory within C:Usersjquilliam2? If so, what’s the contents?

Yes I have a log folder and a file called .writabletesterpath. I have received a different error on other machines “sonic pi is already running? Cant open UDP port 4558”

From: Sam Aaron [mailto:notifications@github.com]
Sent: 26 April 2016 13:23
To: samaaron/sonic-pi
Cc: Josh Quilliam; Author
Subject: Re: [samaaron/sonic-pi] Critical server error — could not connect to server! (#1181)

Wow, that’s very odd — it seems to think you’re running under Linux — something is clearly broken here. Out of interest, do you have a .sonic-pi directory within C:Usersjquilliam2? If so, what’s the contents?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/1181#issuecomment-214722069

Hi, are you using the msi or the portable app?

The msi, I deployed as a GPO, then because it was crashing I removed it and installed manually on a few machines. Should I try the portable? Does it have the same functionality?

From: Sam Aaron [mailto:notifications@github.com]
Sent: 26 April 2016 13:31
To: samaaron/sonic-pi
Cc: Josh Quilliam; Author
Subject: Re: [samaaron/sonic-pi] Critical server error — could not connect to server! (#1181)

Hi, are you using the msi or the portable app?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/1181#issuecomment-214723687

Hi, I’m mostly concerned that the log paths look like this:

C:Usersjquilliam2.sonic-piloggui.log

rather than:

C:Usersjquilliam2.sonic-piloggui.log

notice the missing

I have no idea why this might be.

Ah, it’s just GitHub’s Markdown conversion which is eating it up for some reason. The log paths are correct in their raw form.

Ah I see.

From: Sam Aaron [mailto:notifications@github.com]
Sent: 26 April 2016 13:47
To: samaaron/sonic-pi
Cc: Josh Quilliam; Author
Subject: Re: [samaaron/sonic-pi] Critical server error — could not connect to server! (#1181)

Ah, it’s just GitHub’s Markdown conversion which is eating it up for some reason. The log paths are correct in their raw form.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/1181#issuecomment-214728317

The Linux thing is also a red-herring — that just means the Windows version was compiled against a Qt < 5.4 and therefore the API for asking the OS description isn’t there.

OK, so we know the following:

First time Sonic Pi boots OK
Second time it fails with the above error
After a full Windows reboot, Sonic Pi boots again, but subsequently fails.

Is there anything else youv’e observed?

A few questions:

How are you closing Sonic Pi down between app launches?
After Sonic Pi has launched correctly for the first time — are you able to make sounds via simple commands such as play 70?
Could you try versions v2.9 and v2.8 to se if they exhibit the same behaviour?

Also, could you try the portable app — it should exhibit the same behaviour, but it would be good to get some verification of this.

The only other thing is that it work on one workstation without a problem. But if you copy the run folder to any other machine it give you one of those errors

From: Sam Aaron [mailto:notifications@github.com]
Sent: 26 April 2016 13:55
To: samaaron/sonic-pi
Cc: Josh Quilliam; Author
Subject: Re: [samaaron/sonic-pi] Critical server error — could not connect to server! (#1181)

OK, so we know the following:

First time Sonic Pi boots OK
Second time it fails with the above error
After a full Windows reboot, Sonic Pi boots again, but subsequently fails.

Is there anything else youv’e observed?

A few questions:

How are you closing Sonic Pi down between app launches?
After Sonic Pi has launched correctly for the first time — are you able to make sounds via simple commands such as play 70?
Could you try versions v2.9 and v2.8 to se if they exhibit the same behaviour?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/1181#issuecomment-214731196

Just tried the portable and it also crashes

From: Sam Aaron [mailto:notifications@github.com]
Sent: 26 April 2016 13:57
To: samaaron/sonic-pi
Cc: Josh Quilliam; Author
Subject: Re: [samaaron/sonic-pi] Critical server error — could not connect to server! (#1181)

Also, could you try the portable app — it should exhibit the same behaviour, but it would be good to get some verification of this.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/1181#issuecomment-214731970

Further thoughts:

Could you let me know the contents of the files in the log directory?
If you remove the .sonic-pi directory, does Sonic Pi boot successfully?
Could you list the contents of the log directory immediately after a successful boot and then list the contents out after a failed boot so I can see the difference…

When you reboot and run for the first time and the close down Sonic Pi can you right click your Taskbar and check Task Manager. Do you have Ruby interpreter and scsynth still running as background processes? If so end the processes and start SP again. Does that then work?

Sam — I think C:Usersjquilliam2.sonic-pi is a red herring and the path is correct.

jquilliam — can you open up PowerShell on your machine and enter the following:

cd
cd Usersjquilliam2.sonic-pi

then run the following

Do you get a similar output to the following?

Path      Owner         Access
----      -----         ------
.sonic-pi PC-SSDwinnie NT AUTHORITYSYSTEM Allow  FullControl...

No we don’t they are got when SP closes. PS keeps giving me a error running a ACL past the user folder

From: sccmentor [mailto:notifications@github.com]
Sent: 26 April 2016 14:17
To: samaaron/sonic-pi
Cc: Josh Quilliam; Author
Subject: Re: [samaaron/sonic-pi] Critical server error — could not connect to server! (#1181)

Sam — I think C:Usersjquilliam2.sonic-pil is a red herring and the path is correct.

jquilliam — can you open up PowerShell on your machine and enter the following:

cd Usersjquilliam2.sonic-pi

then run the following

Get-Acl

Do you get a similar output to the following?

Path Owner Access

.sonic-pi PC-SSDwinnie NT AUTHORITYSYSTEM Allow FullControl…

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHubhttps://github.com//issues/1181#issuecomment-214738100

@jquilliam this is starting to look like some sort of filesystem problem.

Would it be at all possible to show me the contents of the files in the log directory after a failed boot? You can just paste them in this conversation (via the GitHub website rather than as an email attachment)

If you like I will send you a zip file of working and failed

From: Sam Aaron [mailto:notifications@github.com]
Sent: 26 April 2016 14:38
To: samaaron/sonic-pi
Cc: Josh Quilliam; Mention
Subject: Re: [samaaron/sonic-pi] Critical server error — could not connect to server! (#1181)

@jquilliamhttps://github.com/jquilliam this is starting to look like some sort of filesystem problem.

Would it be at all possible to show me the contents of the files in the log directory after a failed boot? You can just paste them in this conversation (via the GitHub website rather than as an email attachment)

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com//issues/1181#issuecomment-214747450

Sounds like you have a profile issue rather than a problem with Sonic Pi.

Can you run

cd
cd Usersjquilliam2
Get-Acl

What response do you get back there?

Do you have an admin account on that machine, different to the jquilliam2 account?

Yes the local profile is an administrator. You receive the same errors.

PS results.
[cid:image002.jpg@01D19FCA.C3B8BF90]

From: sccmentor [mailto:notifications@github.com]
Sent: 26 April 2016 14:40
To: samaaron/sonic-pi
Cc: Josh Quilliam; Mention
Subject: Re: [samaaron/sonic-pi] Critical server error — could not connect to server! (#1181)

Sounds like you have a profile issue rather than a problem with Sonic Pi.

Can you run

cd
cd Usersjquilliam2

What response do you get back there?

Do you have an admin account on that machine, different to the jquilliam2 account?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com//issues/1181#issuecomment-214748051

I can’t see an image. Can you paste the error message?

@jquilliam — it looks like you’re responding via email — however we can’t see any email attachments here in the GitHub issue tracker: #1181 (comment)

in the logserver- errors
Non-critical error: Could not load did_you_mean

in logserver-output
Sonic Pi server booting…
Using protocol: udp
This is Sonic Pi v2.10 running on windows with ruby api 2.1.0.
Sonic Pi Server successfully booted.

*In log gui
*
[GUI] — using default editor colours
[GUI] — shutting down any old audio servers…
[GUI] — starting UDP OSC Server on port 4558…
[GUI] — unable to listen to UDP OSC messages on port 4558
[GUI] — booting live coding server
[GUI] — waiting for server to boot…