I have a vps on OVH and I tried to access it by ftp by wanting to configure a Proftpd server, I tried several tutorials without success and I wanted to start from scratch on the installation of said Proftpd too, I 've removed the packages and dependencies.
But after that, my website does not launch anymore, I have the following error: 403 Forbidden You don't have permission to access this resources, Apache/2.4.52 (Ubuntu) Server at cermel.org Port 443,
Could someone here help me please, thank you in advance.
Ulrich
I tried to give the rights to the user and the group but it doesn't change anything, I reviewed the configuration file of the virtual server but it still doesn't work.
Related
I am very new to both aws ec2 instances and postgresql. I was able to get a database up and working for a web application mainly using the phppgadmin interface. Today I was working on my web app and was abruptly disconnected from the database. In my web app I got the error " pg_connect(): Unable to connect to PostgreSQL server: could not connect to server: Connection refused\n Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432?" I now can't log in to phppg admin or connect to postgres from my ec2 instance command line. After inspecting the log file at /var/log/postgresql/postgresql-12-main.log I am seeing the error "FATAL: could not open file "global/pg_filenode.map": Permission denied" followed by "LOG: abnormal database system shutdown" I have my pg_hba.conf and postgresql.conf files are configured correctly as I have been doing work on this database for a few days now. Any help would be appreciated.
You or something else wrecked your PostgreSQL installation by changing permissions on or ownership of PostgreSQL files. On Windows and its interesting concepts of file locking, I'd suspect an anti-virus program, but you seem to be running some kind of Unix. Little more can be said with the little information in the question.
I just got the latest IdentityServer4 and quickstart code and trying to follow the instruction of quickstart to set it up and test. And I am using VS.Net 2019 on my Windows 10 laptop. The setup process seemed to be fine and the code compiled with no issues. But when I run the Client project from VS, I got the error message "Error connecting to https://localhost:5001/.well-known/openid-configuration. No connection could be made because the target machine actively refused it.." at the following line of Client code:
var disco = await client.GetDiscoveryDocumentAsync("https://localhost:5001");
Can someone tell me what I might be missing here? By the way, localhost:5001 should be my identity server and I use https://localhost:6001 for my API.
Per our discussion in the comments, a good first step is to run a telnet test:
telnet localhost 5001
The failed connection showed us that either your server was not running or it was listening on a different port. Ultimately you were able to determine that it was not running, and you concluded that it did not start due to an issue with your IIS Express profile.
After using Team Foundation Server (TFS) for years, we suddenly lost the ability to connect either through Visual Studio (VS) or via URL. To the best of my knowledge, no changes were made to the virtual server that supports TFS.
In VS the error is:
TF400324: TF services are not available from server... Unable to connect to the remote server...
If I use the {server}:8080/tfs or localhost:8080/tfs url in a browser it tells me the connection was refused.
In the SQL Management Studio both the Tfs_Configuration and Tfs_DefaultCollection databases appear to be connected, and show a "Ready" status. In the TFS Administration Console the DefaultCollection state is "Online".
Perhaps the best clue is that if I use netstat to see which ports are in use on the server, port 8080 is not listed at all. Is there a listener service that needs to be started?
I see that the following services are currently disabled: UPnP Device Host, SSDP Discovery, Internet Connection Sharing, SSDP Discovery, Internet Connection Sharing, Smart Card, Routing and Remote Access, Net.Tcp Port Sharing Service, and Computer Browser.
Of course, we have tried a reboot to no avail.
Any troubleshooting suggestions will be much appreciated, as this has begun to impact our productivity. Thanks in advance!
Edition: TFS 2015
Version: 14.114.28805.0 (Update 4.2)
Update:
I should mention that the firewall has been disabled in attempting to diagnose the issue.
Also, there are errors associated with TFS in the Even Viewer, but they are not at all clear. Here are is a snippet:
VssRequestContext.HostManagement.Microsoft.TeamFoundation.JobService.Extensions.Core.IdentitySyncJobExtension.Run:1
Registry.TeamFoundationRegistryService.Write:1
Default.SqlResourceComponent.Execute prc_UpdateRegistry ds:LT-TFS2
db:Tfs_Configuration:2 Default.SqlResourceComponent.Execute:-3
Registry.TeamFoundationRegistryService.Write:-3
GroupComponent.SqlResourceComponent.GetGroupsToSync:3
GroupComponent.SqlResourceComponent.Execute prc_GetGroupsToSync
ds:LT-TFS2 db:Tfs_Configuration:3
GroupComponent.SqlResourceComponent.Execute:-4
GroupComponent.SqlResourceComponent.GetGroupsToSync:-4
GroupComponent.SqlResourceComponent.ReadGroups:4
GroupComponent.SqlResourceComponent.Execute prc_ReadGroups ds:LT-TFS2
db:Tfs_Configuration:4 GroupComponent.SqlResourceComponent.Execute:-5
SOLVED!
I found that the TFS site was disabled within the IIS Manager. When I tried to enable it, it reported that the World Wide Web Publishing Service was disabled. Enabling both resolved the issue.
This error is usually related to TFS cache. You could give a try following below steps:
Close all instances of Visual Studio
Open the Task Manager and check if any TFS Services are running. Select each of them and click on End Process Tree
Browse to the folder %LocalAppData%\Microsoft\Team Foundation\ and then select the folder with your TFS version and go inside
the Cache folder. for example, the path was
%LocalAppData%\Microsoft\Team Foundation\x.0\Cache and it should be
the same on your machine with the difference of the TFS version folder
name.
Delete everything in that Cache folder.
Start Visual Studio and run it with Admin mode.
Besides, in case of your TFS is configured with self-signed TLS/SSL certificate.
If this is the case, you need install that certificate to the Trusted Root Certification Authorities store on the client machine, where you have VS.
For this scenario, you could refer this answer.
Moreover, please also check if there are any errors in the event viewer in your TFS server. This may help to narrow down the issue.
So I know there are a load of questions on SO related to this already, but I think at this point I've read them all, tried all the suggestions, and still haven't found a resolution.
I've got a simple .Net core MVC app with a connection to a local MSSQL database. I have been unable to get it to connect to SQL when running it in a container... I just get an error that a connection couldn't be established. When run in IIS Express it connects fine.
My connection string is:
Data Source=10.11.56.36,1433;Initial Catalog=TestDB;Integrated Security=false;User id=testdb;Password=######;MultipleActiveResultSets=True
My container is launched via:
docker run -it -p 8080:80 testing
Here are the things I've attempted so far:
Ensured the SQL server is configured to accept remote connections
Used "host.docker.internal" for server name
Ping'd the SQL server IP to ensure it's accessible to the container
Verified port 1433 is allowed through the firewall
Tried a different port and configured SQL server to listen on that
Tried without the port in the connection string
There were a host of other things I've tried as well in the last few hours of beating my head on this, but I've made no progress at all. What am I missing?
Any help would be greatly appreciated.
Please check if this bug is the reason for your error, if you are running a Linux Container:
https://github.com/dotnet/corefx/issues/29147
If so, the fix is to add the following to the runtime image in dockerfile
RUN apk add --no-cache icu-libs
ENV DOTNET_SYSTEM_GLOBALIZATION_INVARIANT=false
I just had this issue. I spent 3 days and the fix for me was to use a fully qualified domain name.
MyServerName.MyDomain.com
Has anyone outside of Msft been able to map a drive to the new preview of Azure File Storage shares without having a VPN? Our IT guy has verified that 445 is open outbound and we even contacted Comcast to verify that they are not blocking the traffic.
This is the command we are using and the error we get...
C:\Users\johndoe>net use Y: \\\\myfileshare.file.core.windows.net\\clientapps /u:myfileshare mystoragekey
System error 53 has occurred.
The network path was not found.
AzCopy works fine, but that uses https. We have tried from Windows 2012 Server and a Surface with Windows 8.1. Both support SMB3.0.
Should we be able to test telnet to myfileshare.file.core.windows.net on port 445?
For me it was working on Windows 8 and 10, but not Windows 8.1
I had to change the Group Policy for LAN Manager authentication level to: Send NTLMv2 responses only. I got this info from this MS answer.
https://social.technet.microsoft.com/Forums/en-US/d2ab0015-e7f7-4efb-b539-e1083d5a9d1b/azure-storage-file-service-for-onpremise-net-use-error-53?forum=windowsazuredata
I case you don't know how to open up the policy editor, see this article:
https://technet.microsoft.com/en-us/library/cc731745.aspx
I have the exact same issue. It happens that I can use the command NET USE in some hosts, while in others it gives me an error 53. On another host I actually get an access denied error.
It works fine in one Windows 10. On another 3 I've tried it does not work fine. It also works fine on a Windows 2008 R2 used as a dev environment, but it does not work on others.
I have no problem when using Azure Powershell CMDlets though.
When I called Comcast they told me 445 was blocked. I created an azure vm and confirmed the command was correct. Was able to map my drive fine within Azure. took the same command on-premise and kept getting the same error you mentioned. I would double check that comcast really has the open.