We are getting DNS resolution error on places.sit.ls.hereapi.com during the weekends only. During the week days it is fine. Does anyone else have issues with the here-api places service during the weekends?
Made an api call to places.sit.ls.hereapi.com during the weekend
Expected the call to resolved correctly
Result was "Error resolving DNS name places.sit.ls.hereapi.com"
Try removing the "sit" from the URL, that should work.
places.sit.ls.hereapi.com
Should be
places.ls.hereapi.com
Also, if you have DNS issues please try other DNSs on your end if it keeps failing.
Related
I have been following a tutorial by NetworkChuck setting up SearXNG on Linode so i can "ditch Google". I have followed all the instructions and yet i keep getting this error:
terminal
This in turn, stops the website from working. Does anyone know how to fix this?
In .env, check the value of SEARXNG_HOSTNAME is a valid DNS name.
For reference:
https://caddy.community/t/subject-name-does-not-qualify-for-certificate/10764/7
https://github.com/caddyserver/caddy/issues/3977
Have no clue what ghost-rider is... Error follows.
Lighthouse returned error: generic::internal: Extension result empty.
Lighthouse calling Page.navigate with https://www.redacted.com/blog
Uncaught (in promise) Error: Extension timed out. No call to exit()
before render timeout. at wrs.Extension.onTimeout_
(http://ghost-rider/devtools_script_api.js:5576:13) at
http://ghost-rider/devtools_script_api.js:708:9 at Map.forEach
() at chromium.DevTools.Connection.dispatchMessage
(http://ghost-rider/devtools_script_api.js:707:76) at
chromium.DevTools.Connection.onJsonMessage_
(http://ghost-rider/devtools_script_api.js:689:65) at :1:40
i agree it looks sketchy. i'm getting that same error when running pagespeed on my joomla test site. i grepped 'ghost-rider' on my server and full-text searched my db and can't find that anywhere on the site.
the url doesn't work and the domain ghost-rider is invalid of course. no .com or anything. weird...
running lighthouse on https://www.webpagetest.org/lighthouse gives a timeout after 80 seconds on my site (nothing about ghost-rider). http://gtmetrix.com/ and sites like that seem to work fine and the site loads in about 6-10 secs.
ran an ispp scan and didn't find anything.
nothing else to add... anyone else getting this on pagespeed/lighthouse?
I am having an issue with DotNetNuke platform that I cannot understand for the life of me... Google and SO searches have been no help.
The very first time any user tries to hit the site, regardless of the URL they are requesting, they are redirected to the URL below, and given the 404 error shown below. After that initial 404, if the user requests that exact same URL, everything works perfectly for that user going forward. They are redirected to the correct login page and everything works correctly from that point forward.
Does anyone know why this would only happen on the very first request to the site for each user? I have a Development, Test and Production environments set up, and the issue is consistent across all environments.
Requested URL: http://intranet.domain.com/page
Redirected URL: http://intranet.domain.com/Login.aspx?ReturnUrl=/DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx
Server Error in '/' Application.
The resource cannot be found. Description: HTTP 404. The resource you are looking for (or one of its
dependencies) could have been removed, had its name changed, or is
temporarily unavailable. Please review the following URL and make
sure that it is spelled correctly.
Requested URL: /Login.aspx
IIS: v7
DNN: v7.02.01
Default DNN authentication is disabled and Active Directory Authentication module is enabled. (v5.0.6)
Please let me know if there is any other configuration information I can provide.
This is not a full solution however it should help shed some light on the situation. I experienced the same issue. I would go to the website and it would redirect me to
WebsiteLinkHere/DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx
On removal of the
DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx
it would take me to my homepage and everything acted as expected from there on out. I grabbed the latest sourcecode from github for this module and started debugging. I traced the error down to the DNNUserController.ValidateUser() function. This seems to be returning nothing which then causes the page to error out. I decided to add a bandaid fix for the time being which may help others.
Within the WindowsSignin.aspx.vb file I added a try catch around
objAuthentication.AuthenticationLogon()
Within the catch statement I added the code that is used to redirect you after a successful authentication to the page you came from.
Try
objAuthentication.AuthenticationLogon()
Catch
Dim querystringparams As String = "logon=" & DateTime.Now.Ticks.ToString()
Dim strUrl As String = DotNetNuke.Common.NavigateURL(DotNetNuke.Entities.Portals.PortalSettings.Current.ActiveTab.TabID, String.Empty, querystringparams)
If Not HttpContext.Current.Request.Cookies("DNNReturnTo") Is Nothing _
Then
querystringparams =
HttpContext.Current.Request.Cookies("DNNReturnTo").Value
'ACD-8445
If querystringparams <> String.Empty Then querystringparams = querystringparams.ToLower
If querystringparams <> String.Empty And querystringparams.IndexOf("windowssignin.aspx") < 0 Then _
strUrl = querystringparams
End If
HttpContext.Current.Response.Redirect(strUrl, True)
End Try
This is not an elegant solution however it does escape the issue of the user's initial visit to the site being an error screen. Everything else seems to work as expected after the initial visit.
I finally found the answer over two years later...
The problem was solved by commenting out "add name="Authentication" ..." line in web.config. This disabled autologin feature completely.
http://www.dnnsoftware.com/forums/threadid/459907/scope/posts/site-redirecting-to-desktopmodules-authenticationservices-activedirectory-windowssigninaspx
Mates, two days ago, the webhosting of a site i'm administrating went down.
Now it seems to be back working, but when I try to acces to wp-admin i recieve the following error message:
Parse error: syntax error, unexpected T_ENCAPSED_AND_WHITESPACE,
expecting T_STRING or T_VARIABLE or T_NUM_STRING in
/home/ohmycut/public_html/wp-settings.php on line 80
These are lines from 75 to 85:
// Include the wpdb class and, if present, a db.php database drop-in.
require_wp_db();
// Set the database table prefix and the format specifiers for database table columns.
$GLOBALS['table_prefix'] = $table_prefix;
wp_set_wpdb_vars();
// Start the WordPress object cache, or an external object cache if the drop-in is present.
wp_start_object_cache();
I, honestly, don't understand why am i getting this error.
Any ideas?
thanks!
Try contacting the web hosting service to see if they can revert it to a state before the service went down.
Since changing my server hosting to a new provider (ovh),
I don't manage to get the client's IP using a simple Request.ServerVariables["REMOTE_HOST"] .
It always returns 10.0.1xx.2xx (masked the exact value, don't know if that matters) which seems like an internal server IP to me.
Calling Request.ServerVariables["REMOTE_ADDR"] and Request.ServerVariables["LOCAL_ADDR"] gives the same results.
The code is called from withing Global.asax if that is relevant.
Any idea ?
I've had same problem today with OVH.
Seems Request.ServerVariables["HTTP_REMOTE_IP"] return the good ip