Gh Configure

[Roshan Fried]

Ihave a "new to me" R610 with Unleashed 200.13.6.1.319. Upon receipt I reset to default via button in rear. Configure.Me-xxxxxx appeared but no device I tried was able to connect. Using Ethernet, I was able to reach web GUI on 192.168.0.1 and was presented with initial setup. For testing purposes, I simply made a new Wifi network called "TestWifi", finished the setup and rebooted. Upon next startup TestWifi is not seen, but Configure.Me remains.

No device was still able to use that SSID, so I again used Ethernet and browsed the GUI settings. Everything appeared OK, but it did show zero working access points. Tried setting to factory defaults again, but that had same issue. Tried reflashing the same firmware and after reboot and setup, the same issue remains. Access point appears stuck with Configure.Me and will not broadcast any other Wifi networks configured on device. Any ideas?

For reference I tried connecting to Configure.Me with two Win10 laptops, an older Win7 laptop, an iPhone with IOS 16.x and attempting to use the Ruckus app. Also tried an Android tablet. Nothing appears to connect to the Configure.Me SSID, only Ethernet works. Lastly, FWIW I also tried three diff power adapters that are known to work.

Additional update: AP appears to be working as expected. The issue is still repeatable if the AP is reset to defaults - unable to connect to Configure.Me, zero working APs and configured Wi-Fi networks not broadcasting. This was easily remedied by changing Admin/Services System IP settings from DHCP to Manual (same IP) and rebooting. Also, from a factory defaulted state, a restore of previously saved backup also puts AP in correctly saved config without need to change IP settings.

I reset to defaults again (from inside GUI), which still didn't help. Also tried reset to defaults from CLI via SSH (some claim you need to do this to truly reset), "set factory" command didn't work. Then I tried flashing various supported Unleashed versions, which didn't take (upload successful, but didn't process and complete update).

Finally I changed IP settings on AP from DHCP to manual and choose a different subnet (from 0.1 to 10.1). AP immediately rebooted and oddly took almost 20mins to completely come up. Once online I logged in and noticed the GUI finally showed an active and working access point. No longer was Configure.Me broadcasting and I was able to create and see a new wireless network.

In my survey I have multiple questions that require a number as input. When looking at the survey answer results, the questions that require a number input have the following text: 'Please enable editing and configure widget'. I have no clue what is meant with this.

This page ( -do-i-acitvate-a-widget-with-text-iq) has the same problem, but I do not understand the instructions that are given to solve it. I do not know where to find dashboard settings - text as the solution states. Could anyone please instruct me on how I solve this so that I can see the answers to the question in the results?

I have the same problem.

Why is there an obscure error message given with no guidance on what to do?

Why would each individual who has this problem be directed to contact support rather than posting a solution that makes things quicker for us, and reduces the burden on support. Even if there isn't a universal solution it would help to know that.

I just had this same issue and wanted to provide the answer on how to proceed. When you switch the chart type, the metrics will disappear and you will get the error message to enable editing and configure the widget. In order to fix it, you will need to re-add the metrics. I've included the screen shots below. Just populate the fields with the metrics you want to use.

It is possible that some software in your environment may have created redfish subscriptions that may be resulting in this behavior. Worse case scenario for this problem will likely require a factory reset of the iLO to resolve. A factory reset of the iLO will wipe out all configuration settings, so this should be done with care. You can always reconfigure the iLO, but the default iLO password will need to be obtained from the pull tab on the front of the server.

You might want to consider creating a new topic by utilizing the "New Discussion" button if you are facing any issues, as this will not only enhance visibility compared to the old topic but also boost your chances of receiving responses from experts.

3-i follow this course to configure the GlobalProtect ( -Articles/Basic-GlobalProtect-Configuration-with-U...). ==> this toturial is for configuring the (paloalto wan interface) as a portal and getway globalportal, it woking for me at this point.

your globalprotect tunnel will then run over ssl. If you want to use GP over ipsec or x-auth then you will need to add further port forwarding as above for udp 500 and udp 4501. But ssl 443 will work ok.

Miclball, yes you are right, it was a port forwording problem, also a ceritificate problem, i configured the port forwording, and i run the adsl wan interface certificate on globalprotect Portal&getway (cos it gave a certificate error).

The configure script configures the source tree for compiling and installing the Apache HTTP Server on your particular platform. Various options allow the compilation of a server corresponding to your personal requirements.

Most modules are compiled by default and have to be disabled explicitly or by using the keyword few (see --enable-modules, --enable-mods-shared and --enable-mods-static below for further explanation) or --enable-modules=none to be removed as a group.

To find out which modules are compiled by default, run ./configure -h or ./configure --help and look under Optional Features. Suppose you are interested in mod_example1 and mod_example2, and you see this:

Multi-Processing Modules, or MPMs, implement the basic behavior of the server. A single MPM must be active in order for the server to function. The list of available MPMs appears on the module index page.

Choose the default MPM for your server. If MPMs are built as DSO modules (see --enable-mpms-shared), this directive selects the MPM which will be loaded in the default configuration file. Otherwise, this directive selects the only available MPM, which will be statically linked into the server.

Add one or more third-party modules to the list of statically linked modules. The module source file module-file will be searched in the modules/module-type subdirectory of your Apache HTTP server source tree. If it is not found there configure is considering module-file to be an absolute file path and tries to copy the source file into the module-type subdirectory. If the subdirectory doesn't exist it will be created and populated with a standard Makefile.in.

The LoadModule directives for the chosen modules will be automatically generated in the main configuration file. By default, all those directives will be commented out except for the modules that are either required or explicitly selected by a configure --enable-foo argument. You can change the set of loaded modules by activating or deactivating the LoadModule directives in httpd.conf. In addition the LoadModule directives for all built modules can be activated via the configure option --enable-load-all-modules.

Several features of the Apache HTTP Server, including mod_authn_dbm and mod_rewrite's DBM RewriteMap use simple key/value databases for quick lookups of information. SDBM is included in the APU, so this database is always available. If you would like to use other database types, use the following options to enable them:

I have a situation where my server is running on a non ssl cert. This is causing me to not be able to use Forms via mobile app. Which means we are paying for a service I cannot get to work for the end users.

The scariest part was when I tried logging into Formsconfig/LFDS/STS, the username and password was not accepted. Which I am certain are the correct credentials, the credentials were used on the previous config, don't know if this changes when using a new cert?

At this point I did not know what I was doing wrong or right anymore. I checked user access rights to all the local files, and thought, how can this be the cause since the other cert works perfectly fine with the current user rights? And I ruled this out.

It sounds like you are running into a mix of dns and certificate problems. I would suggest going back to http everywhere (what I think you mean by "running on a non ssl cert"?) and first switch to using FQDNs. You'll need to register in dns the .co.za addresses that are failing to resolve. This switch is probably also the cause for the "unauthorized login screens" you are seeing, since Windows authentication works differently with FQDN. You might need to add the sites to your trusted sites. Is there a reason you are resorting to editing the hosts file instead of using dns?

Once you're working with FQDN it should not be too difficult to load certificates issued to those names into those servers, and update the applications to use HTTPS. What are you using as your CA? Remember that not only does the cert have to match the host name, but the cert has to be trusted by the client.

The reason for me editing the hosts file is simply because I do not have a decent understanding of how to configure this properly. I did it as a step to see if I can get this whole thing working. I am not 100% sure what that file's purpose is to be honest. - Didn't do much research, just want to get my services working.

3a8082e126