New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 772109 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

http://www.slimsworkshop.com/wp-admin Too long will not open

Reported by thephant...@gmail.com, Oct 5 2017

Issue description

Chrome Version       : 61.0.3163.100
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5:
  Firefox 4.x:
     IE 7/8/9:

What steps will reproduce the problem?
1.
2.
3.

What is the expected result? should open in edit mode when user and password entered 


What happens instead of that? This site can't be reached - took too long to respond (ERR_CONNECTION_TIMED_OUT) 


Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36



 
chrome-net-export-log.json
1.2 MB View Download
This issue occurs when I install a wordpress on a new domain. I cannot open the DoMain/wp-admin 
cet this error This site can't be reached - took too long to respond (ERR_CONNECTION_TIMED_OUT) 
Cc: divya.pa...@techmahindra.com
Labels: Needs-Triage-M61 Needs-Feedback Triaged-ET
@ thephantom225: Could you please provide test accounts to access http://www.slimsworkshop.com/wp-admin, which will help us in triaging the issue from TE-end
It opens for me now
Project Member

Comment 4 by sheriffbot@chromium.org, Oct 6 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "divya.padigela@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)
Marking this issue as 'Won'tFix' based on the C#3. Please feel free to add a new issue if the issue is observed.
Thanks!

Sign in to add a comment