I usually don't have any problem with Laragon as it works pretty good. I had no problem using Laravel.
But recently, my laptop made a Windows update, and since it restarted, nothing works anymore.
By nothing, I mean that when I try to load my virtual host "foo.dev", I have a 500 error without any info. So I tried the old way by going on localhost/www/foo/public and it loaded my website. Great !
But new bad news, impossible to connect to the database, even using a software, as if the password had been changed...
I don't have any idea on how to fix these problems and where does the problem comes from...So I'm asking for your help, if anyone has already faced a similar problem and reached to solve it.
Thank you.
I guess when updated your windows, Chrom also updated and apparently Chrome made new release that forces .dev, .app, and a few other TLDs to use HTTPS. The best fix is to use .local instead of another TLD.
see this question for more info
I've created a Laravel booking application that is currently being used in schools. When I test the live (production) version of the website on my own machine, the application works fine.
However, some schools are reporting that they are not even able to see the initial login screen, and are getting the Laravel 'Whoops, something went wrong' screen. I can confirm that the school firewall is not causing the issue, and that the website has worked ok in the past.
What reasons could there be for the same code to work on my machine but not on the live version? So far I have tried resetting the browser cache, and also flushed the DNS but to no avail...
Any suggestion are welcome.
Thanks.
It seems like folder permissions problem.
As the error is not shown, nobody can really help you..
What I suggest, is first to check the log file (storage/logs/laravel***.log).
There you should be able normally to see the problem and then you can fix it.
Another solution, in your ".env" file, switch from production to development mode, so you can be able to see the exception.
Check capitialization on the view name. I've had issues where everything works fine locally, but then get not found issues when live as the server behaves differently and is case sensitive.
My email address has changed and now I can't log into Visual Studio 2017.
The error is "We could not refresh the credentials for the account. Failed to refresh the access token".
How can I fix this?
This bug will be fixed in a future version.
For now:
Close down VS2017
Go to "C:\Users\{username}\AppData\Local\.IdentityService"
Rename "IdentityServiceAdalCache.cache" as shown below. (for example just add an underscore to it)
Restart VS2017 and log in.
NOTE: There are similar issues that this won't resolve, but this worked for me.
Open Visual Studio. Click Help, Send Feedback, Report a Problem...
This brings you to a login screen. If you log in from there, it will log you into Visual Studio.
What worked for me was to rename .identityservice and then restart VS and log in to your VSTS account. It then recreates a new .identityservice that it can access.
I tried by deleting only the IdentityServiceAdalCache.cache as in the accepted answer but it did not fix the problem.
For the record, I managed to fix it by deleting every files within the .IdentityService folder (located in C:\Users{username}\AppData\Local.IdentityService).
I have read dozens of posts on this topic discussing clearing out .IdentityService. I tried every variation of this solution that one might think of. None worked.
I ended up poking around and trying to manually login to my Microsoft account using Internet Explorer, but I could not connect to https://login.microsoftonline.com. I added the https://login.microsoftonline.com address to my Trusted Sites in Internet Options. Once I had done this, Visual Studio was able to connect to Microsoft and validate my account.
When an error occurs, Visual studio will log it's error messages in the following folder. Please check the logs located at
%Temp%\servicehub\logs
This can also be caused by network restrictions. Please disable your virus guard or firewall and check.
This issue can also be caused by running VS "As Administrator" and the administrator is a different user. Just some FYI.
None of these answers will resolve that issue unfortunately.
Very old thread but if someone is still having this issue, then try following in my footsteps:
I just deleted the entire .IdentityService folder, and launched visual studio again... It asks you to log in and works normally. (for me)
Make sure you can access https://login.microsoftonline.com
If your network is blocking that (perhaps to block Microsoft webmail), then the above solutions will not pertain to you. Either unrestrict access, or you will need some off-line version.
In case someone is still looking for an answer. What worked for me was checking that the AppData folder and Local folder were not on 'read only mode' in the path "C:\Users{username}\AppData\Local.IdentityService" and it just worked!
Check to make sure that your PC no limit(IP-Firewall) to Internet connection access.
Disable or turn off VPN
It happened to me when using an account that uses my organization's email-domain, and I guess it tried to verify it and it couldn't find it in their database, and as soon as I used an account with a onmicrosoft.com domain, it worked.
The interesting part is that it allowed me to create the Microsoft account with this organization email and I still use it for DevOps, and it just stopped me when signing in with Visual Studio, I don't understand why this difference is.
I hope this can help someone..
I have VS 2017 and had this exact issue. Simply deleting
C:\Users\{username}\AppData\Local.IdentityService did not work for me.
Follow the steps 1-2 below to see if you might have and identical cause of the problem, and the rest how to solved it if so.
Go to C:\Users\{user}\AppData\Local\Temp\servicehub\logs and open the latest error logs from VS.
IF you see "Retrieved tenant memberships, found '2' owned tenants", then follow the rest of the steps.
Go to azure portal then login under the username you are
trying to use.
The following steps may change by the time you read this, but you
want to get to step 6. Go to Manage Azure Directory.
Click "Switch Tenants"
I was linked to 2 tenants, one of which I did not need. This is what had been causing my issues. Select the useless tenants, and click "leave tenant".
Once this is completed, close all instances of VS.
Delete C:\Users\{username}\AppData\Local.IdentityService.
Open VS and login to your account.
I found the same behavior when using Administrator user.
Any other user can login and activate the license only for himself.
I don't think there is a way to activate for Administrator, which makes using this licensing awkward for usage in a shared resource (i.e. build server).
The one solution which worked for me was resetting the domain password and restarting the system.
I just wanted to share this because i was struggling with the same problem since 8 days tried everything on net and this worked.
Hope it helps someone :)
I updated Visual Studio with latest package and after rebooting my PC issue was solved. I was able to log-in
Opening VS as admin worked for me, none of the above did
I was getting this error from our proxy having restrictive rules in place, I was able to add the sites to a whitelist that were being blocked while trying to login.
Some of the sites I whitelisted in Webmarshal were:
*.windows.net
*.msocsp.com
*.ws.symantec.com
*.digicert.com
*.clicktale.net
app.vssps.visualstudio.com
demdex.net
For me it was due wrong system time, after setting correct time it got fixed automatically
I had the problem of not being able to sign in to VS after not using unity for a long time and then updating everything. The way I solved it was to open VS and then click help. This opened the sign in box with 'Personalization Account'. I clicked 'Account options' under the afore mentioned heading, and changed the 'Embedded web browser' to 'System web browser' in the right window. This enabled me to log in via my Edge browser and everything worked fine.
I just fixed it by changing folder to be public.
folder files: "C:\Users{username}\AppData\Local.IdentityService"
right click and choose property and uncheck the hidden and apply it.
If you are under a domain network there is a workaround (quick fix),
Adding or changing the following key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb
ProtectionPolicy = 1 (DWORD)
Check the most recent modified files at %temp%\servicehub\logs.
Check StorageUtilitiesSingleton-10788-lqnuymos-1.log
For an error like this: The computer must be trusted for delegation and the current user account must be configured to allow delegation.
If that is the case this might help you.
I has this issue recently.
Tried all the options above, none worked.
Get it sorted, after repairing Visual Studio, doing all the updates, restart and updated again, restart, another repair and bang! Worked like a charm.
Instead of doing all this, change embedded broswer to system browser so it will works normally in default browser and gets updated in VS.
In VS 2019 enabling System Web Browser instead of Embedded web browser fixed it for me,
Hope this helps someone
https://learn.microsoft.com/en-us/visualstudio/ide/work-with-multi-factor-authentication?view=vs-2019
I tried multiple things above such as
Renaming c:\users[user]\appdata\local.IdentityService
Logging directly in https://login.microsoftonline.com (noticed certificate issues)
Adding https://login.microsoftonline.com to the Trust Sites list in Internet Options
Opening VS as non-admin as well as admin
Reviewed the logs here: %Temp%\servicehub\logs
I also installed Chrome, setting it to the default browser, because many features were saying IE is no longer supported
Reviewing the logs gave me the clue I needed to solve my particular issue. The log stated there was an issue with SSL trust.
Consequently, I ran our local version of rootsupd.exe and installed any related Microsoft root certificates such as the DigiCert Global Root G2 to the Trusted Root Authorities. After rebooting my machine, I noticed VS began recognizing my account and was actually already signed in.
I couldn't be able to login to XCode accounts using my apple ID. It was working before. When I tried to login it shows an error There was an error connecting to Apple ID Server. But I have logged into the same account from another mac without any issue. Please help me with this. I am using XCode version 8.3.3
try these basic ways may be it will help full
Restart your system,sometimes the simplest turning off and on can
fix this error directly.
Sometimes it happens due to the poor Internet connection, check
whether connection is working properly.
Make sure that the date, time, and time zone are set correctly.
Apple discussion says you should check your firewall and antivirus settings - there may be
a similar rule or setting blocking the ID server
In my case, I upgraded my Xcode and Mac OS to the latest version and it started working smoothly
Charles proxy was the cause for me. Make sure you disable/uncheck HTTP( WebProxy) and HTTPS( Secure Web Proxy) and give it a try
When I click on Store Menu -> Associate App with the Store ... OR Create App Packages I got the following error:
An unexpected network error has occurred. The app list cannot be refreshed. Please retry by pressing the Refresh button.
Even I can't upload the appx files because it fails when checking the app identity and publisher ...
I appreciate your help
Thanks
Sam
We are facing the same issue. This thread here says something about large number of apps that could be the reason. We have only 3 apps on the list. So it doesn't really seem to be the reason. Its the same with both Windows Phone and the Store apps. Accessing dashboard in the browser seems to be unaffected.
Also, I tried different ISPs to rule out that reason.
There seems to be a store problem. I'm talking to Microsoft's support, trying to get a feedback for the service to be back up.
Update:
Microsoft seems to have fixed the issue, which really was on their side.
Please, try again, as it should be all ok now. I've tested and it is all working.
I was facing this issue for the last 2 days. It works fine now. It was probably due to the account migration(so not all user would have faced this issue) and unrelated to the count of apps.
Can you try again?
Thank you all, it seems to be working now, MS fixed the issue.