authpuppy "The node you're trying to access does not exist on the server" - authentication

somebody can help me, how configure wifidog gateway to authpuppy, coz when user connect always notif error "The node you're trying to access does not exist on the server"

You have to create a node so that when request goes to authpuppy it can refer you to a specific node i.e the configured router.
Steps to Create a Node
Manage Nodes
Create Node
Name the node exactly what you named the Gateway Id when you
configured Router in wifidog.conf file
save it
Then Connect to wifi Your problem be solved

Related

Microsoft SQL 2019 (CU16) Always-on issues

I have 2 issues on two different environments, created on the same way, with Local Admin credentials, and added with an account that have Domain admin rights.
Environment #1:
One of them it that looking on the secondary node, i see a ? (questionmark) under Availability Replicas for the Primary node, and i do not have the text "Primary" as on the primary node . That's new for me. What access rights are missing ?
Environment #2 (witch does not work failing over):
When trying to add the listener i get this:
Cluster network name resource 'Listenername, clustername' encountered an error enabling the network name on this node. The reason for the failure was:
'Unable to obtain a logon token'.
?

Google Compute Engine - SSH connection failed after resizing the instance

I'm having troubles connecting to an instance on Compute Engine via SSH.
If I try via command line I get the following error:
Permission denied (publickey)
The same happens if I connect via browser interactive console.
In the serial port output I see:
Mar 22 14:17:04 metadata sshd[9260]: Invalid user name_lastname from xx.xx.xx.xx
Mar 22 14:17:04 metadata sshd[9260]: input_userauth_request: invalid user name_lastname [preauth]
The strange fact is that some minutes ago I didn't have any problem connecting to it and it started occurring after I have resized the instance (changed machine type from small to n1-standard-2).
The boot disk is not full and I haven't modified any user.
I've also tried to add the firewall rule but it doesn't work. I have several other machines on the same project and I can connect to them properly.
I can connect to the interactive serial console using another user previously created on the machine (manually), but I cannot become root from that.
Thanks a lot.
You should be able to login to your instance from the serial console as root user. If you can login as root user, then you can modify the users.
If you cannot login to your instance as root user, then you should create a new instance and copy the data from the old instance to the new instance. You can do this by attaching the disk from the old instance to the new instance

FlowGear IMAP Watcher Node

I've configured an IMAP Watcher Node to point at a Gmail-based account. The Test of the connection returns success. However, when I run the node in the design tool, I get this error:
IMAP Watcher(v1.0.1.6): An operation requiring Environment permission
was denied. Check Node Connection and properties or consider using a
DropPoint.
I imagine the "permission" it needs is to move the processed message from the Watch folder to the Processed folder. It's connecting to the mailbox with the credentials of the mailbox owner. Why would permissions be denied?
Please help.

VisualSVN Server : get /svnindex.xsl forbidden while accessing from browser

We have configured the visualsvn server in remote machine, while accessing the repository from the browser in our local machine, we are getting the below error in the internet explorer browser
'The XML page cannot be displayed'
Cannot view XML input using XSL style sheet. Please correct the error and
then click the Refresh button, or try again later
In the server machine's Event viewer, we found the log 'get /svnindex.xsl forbidden'.
Please note that we are able to connect the repository in TortoiseSVN & other subversion command line tools.
Is any setup or permission is needed to browse the repository in the browser ?
The account that runs VisualSVN Server service (the account is "Network Service" by default) must have Read & Execute permissions to %VISUALSVN_SERVER%. It seems that in your case the account does not have Read access to %VISUALSVN_SERVER%htdocs or %VISUALSVN_SERVER%htdocs\svnindex.xsl. Check the permissions in order to solve the issue.
Read the article KB37: Permissions required to run VisualSVN Server for more information.

Why is WLST not recognizing the user/password in the key and config file in connect() call?

I'm trying to connect to an admin server in WLST using config and key files. There are no error messages but I am prompted for a username and password. These files were created (by another developer who is long gone[1]) with the storeUserConfig() command. My call to connect looks something like this: connect(userConfigFile=configFile, userKeyFile=keyFile, url='t3://somehost:7031')).
Is there some restriction in using these files, such as it can only be used on the host where created, or it needs access to the domain's boot.properties file?
Note: I'm trying to connect to an admin server on a different host and non-standard port (e.g. not 7001). The server I am running WLST on and the remote host are the same version of Weblogic.
Some of the things I have tried:
verified that these files appear correct, the key file being binary data and the config file having a line for "weblogic.management.username={AES}..." and "weblogic.management.password={AES}...".
verified that there is a server on the specified port by entering a known login and password that is successful
specified the admin server in the connect parameter
turn on debug(true); the only output is <wlst-debug> connect : Will check if userConfig and userKeyFile should be used to connect to the server and another line giving the path to the userConfig file
turn on Python logging in jython with -Dpython.verbose=debug; nothing relevant to decryption operation
Munging the key or the config files generates no error messages and behaviour as above
[1]: These files are still used today by other existing WLST scripts. However, these scripts are so convoluted and deliberately obfuscated that they are very difficult to reverse-engineer how connect() is being called.
You do not need to access to the domain's boot.properties file. You just need to make sure the configFile and keyFile pointing to the right files. FYI, here is one of the commands we are using:connect(userConfigFile='./user.secure',userKeyFile='./key.secure',url='t3://somehost:7001')
Have you check the network connectity that might be having a firewall in between that troubling you, check the traceroute from the script machine to the Remote machine. Recently I have faced simalar issue. once the routing table updated with allow the WL admin server port everything got set.
Hope this could helps you!
I had this problem too. In a script, I exported the Linux variables userConfigFile and userKeyFile. Then I connected by running:
url='t3://localhost:7002'
userConfigFile='$userConfigFile'
userKeyFile='$userKeyFile'
connect(userConfigFile=$userConfigFile, userKeyFile=#userKeyFile, url=url)
That all worked in a script, but would not work interactively. I changed to doing the following:
url='t3://localhost:7002'
userConfigFile='/users/me/weblogic-2014/weblogic-admin-WebLogicConfig.properties'
userKeyFile='/users/me/weblogic-2014/weblogic-admin-WebLogicKey.properties'
connect(userConfigFile=userConfigFile, userKeyFile=userKeyFile, url=url)
And that worked interactively.