@dan Hey thanks for replying. Didn't see anything in the logs but in a weird way you got me going in the right direction. I thought when you open a port in the security groups for an EC2 instance it opens that port in the Windows firewall as well. It didn't. I RDP into my instance and manually opened the port 9011 in the firewall. From there I was able to connect via http://IPADDRESS:9011.
Thanks again!
Hello All,
I am trying to connect to the fusionauth dashboard. This is not a fusionauth issue as I can RDP into the ec2 instance and bring it up locally at localhost:9011. When trying to access it from http://IPADDRESS:9011 it just times out and https://IPADDRESS:9013 is the same. Just looking for suggestions for things to try from the community.
My setup is a Windows instance on AWS EC2 and running Fusionauth 1.42.0. I have opened up TCP port 9011 from any IP in the security groups. I think I have even tried opening up every port from any IP with the same results. Trying to access by hostname doesn't work either. The website in general works but I am going to switch from Cognito to Fusionauth. I remember when I had GoDaddy as my host and using fusionauth I didn't have this problem. Not sure what the difference would be.
My skill level is not the highest and I am sure this is something I am overlooking but I am not sure what else to try.
Any suggestions would be appreciated. Thanks.
@joshua Thanks for the reply. Actually I was trying to do the opposite. If a person changed their email I was going to mark "verified" as false until they clicked on the email link I send out to verify it. Being able to programmatically toggle it either way would be preferable so I could customize the flow as I see fit. Hopefully it is wanted enough that it makes it to a future version. I have already given my 
to the github issue. Thanks!
Hi Dan,
I followed this format almost exactly and have had great success patching user information. However, trying to change one value is giving me problems. I am trying to patch user.verified using this code:
Dictionary<string, object> verified = new Dictionary<string, object>
{
{"verified", false}
};
It comes back with a status code of 200 but it never updates the value. Any other key updates without problems. Is this value updatable or is my format wrong? I've tried using the false boolean and even "false" with no luck. Any help would be appreciated.
I gave my thumbs up. I know there are people out there either with strong spam filters that might miss the verification email, or they are just apathetic and never click on it. Either way a manual process would be nice. I agree that I prefer to have it programmatically get verified or have the user do it themselves. This request is for the outlying situations. Auth0 had this feature and that's probably what I am confusing it with. Thanks!
Thanks for replying. I am following up to let you know what happened. I clean installed 1.29 and the mysql connector J file was there but I received that error. I copied the file from a known working install of fusionauth, it prompted me to overwrite the current file which I accepted but I still received that error. After troubleshooting some more I gave up and did a clean uninstall/reinstall.
This time the mysql connector J file was not there. I copied the same file from the known working install of fusionauth and everything worked. I can't explain why but a full uninstall/reinstall and copying the mysql file fixed my issue. Maybe this can help someone else!
Is there a way to manually mark an email as verified? I am running 1.29 and I swore it was available in an earlier version. I just want to be able to verify a users email address by clicking on a button or something in the fusionauth dashboard and mark the user email verified. I feel like I am missing something.
Since this topic was never followed up by the user and never closed I thought I would ask this question instead of opening a new topic.
I am getting the same error after fresh installing 1.29 on my Windows VPS. I verified that the mysql-connector-jar-8.0.21 is in the webinf/lib folder. Obviously I downloaded fusionauth off the site so a network connection is available. What am I missing? What else can I check? This is happening when first connecting to Maintenance Mode.
They can (and I prefer) to have them login with an email address. We use the username to differentiate and display the user without exposing their email address.
We only take the username, email and password to register. I was hoping to use as much of your prebuilt objects as possible without creating our own. No worries as that is what I will do. Thanks for your feedback!
Is there a way to have username, email and password for registration without buying a Reactor license or creating my own login form? Startup project with no budget leaves me with few options. Thanks!
I'm sure the support guys will chime in shortly but you can modify the JWT information with lambdas. Here is the link...
I am using the community version of FusionAuth 1.25 and when setting up self registration I am choosing to log in with username and to verify registration. Since I am using logging in with username it doesn't let a person enter an email when registering. How does it verify then? I think password and username required during registration should be automatic but I don't see that option or am I missing a step? Thanks.
Success! While I would have thought letting FusionAuth create the database would have set the character set in the database, the actual problem was setting the character set for the MySQL server and then restarting the server.
I appreciate your time and patience!
I did a complete uninstall and clean install for this. Same problems. The database name is fusionauth and I let FusionAuth create it, not me. The first attempt is when it first stops, no errors but like I ran Maintenance Mode for the first time. Admin credentials field and password are blank and ordinary user of fusionauth has a new password showing. Second attempt is trying to login again with admin credentials.
Output too long to put in here so I created a pastbin. Let me know if you can't see it. Sorry for the long log file I didn't know which output is relevant.
Whatever happens after the database is created and the schema is set and ordinary user is created is when it stops, goes back into Maintenance Mode and asks for credentials where it can't connect.
I can connect to the MySQL instance (port 3306) with super user. I cannot connect to Plesk instance with super user (port 8306). If I set maintenance mode to use port 8306 and .properties file to 8306 port it will create the database in that directory and then stop the process the same way.
MySQL my.ini
[MySQLD]
port=3306
basedir=C:\\Program Files\\MySQL\\MySQL Server 5.7\\
datadir=C:\\Program Files (x86)\\Plesk\\Databases\\MySQL\\Data
character-set-server=latin1
default-storage-engine=INNODB
read_buffer_size=1M
read_rnd_buffer_size=256K
sort_buffer_size=256K
innodb_flush_log_at_trx_commit=1
innodb_log_buffer_size=1M
innodb_buffer_pool_size=16M
innodb_log_file_size=10M
innodb_thread_concurrency=8
max_connections=151
old_passwords=0
max_user_connections=30
thread_cache_size=4
thread_stack=196608
binlog_cache_size=32768
net_read_timeout=30
net_retry_count=10
net_write_timeout=30
open_files_limit=4161
table_definition_cache=400
[client]
port=3306
Plesk my.ini
# Copyright 1999-2019. Plesk International GmbH. All rights reserved.
# Note that any changes made to this file will be overwritten when Plesk is updated.
[client]
port=8306
[PleskSQLServer]
port=8306
character-set-server=latin1
default-storage-engine=INNODB
query_cache_size=8M
table_open_cache=32
tmp_table_size=7M
thread_cache_size=32
myisam_max_sort_file_size=100G
myisam_sort_buffer_size=2M
key_buffer_size=2M
read_buffer_size=1M
read_rnd_buffer_size=256K
sort_buffer_size=256K
innodb_flush_log_at_trx_commit=1
innodb_log_buffer_size=1M
innodb_buffer_pool_size=16M
innodb_log_file_size=10M
innodb_thread_concurrency=8
max_connections=300
max_allowed_packet=1M
net_buffer_length=4K
old_passwords=0
connect_timeout=20
basedir=C:\\Program Files (x86)\\Plesk\\MySQL
datadir=C:\\Program Files (x86)\\Plesk\\MySQL\\Data
tmpdir=C:\\Program Files (x86)\\Plesk\\MySQL\\Data
Thanks for sticking around and giving this an attempt to work. Any reason why you think a log file isn't being created?
database.url=jdbc:mysql://localhost:3306/fa?serverTimezone=UTC&useSSL=false&allowPublicKeyRetrieval=true
This is the URL fusionauth built. I've tried the Plesk port and it built another fa database and then gave the same error. I've looked for MySQL logs but didn't see anything. To be honest I am not sure where to look for them. I've included the properties code but removed the fusionauth password.
#
# Copyright (c) 2018-2020, FusionAuth, All Rights Reserved
#
#------------------------------------------------------------------------------
# Database
# - Specify the URL and credentials for your database here
# - Required on each node running FusionAuth App webservice
#------------------------------------------------------------------------------
database.url=jdbc:mysql://localhost:3306/fa?serverTimezone=UTC&useSSL=false&allowPublicKeyRetrieval=true
database.username=fusionauth
database.password=
#------------------------------------------------------------------------------
# Additional MySQL database settings.
# - When enabled, FusionAuth will ensure the necessary 'utf8mb4' configuration parameters to
# properly handle 4 byte unicode characters. FusionAuth will fail to start if not configured properly.
# - This value is ignored if using PostgreSQL
# - Only set to false if you understand the limitations not using 'utf8mb4' character sets.
#------------------------------------------------------------------------------
database.mysql.enforce-utf8mb4=true
database.mysql.connector-version=8.0.18
#------------------------------------------------------------------------------
# fusionauth-search
# - Required on each node running FusionAuth Search
#------------------------------------------------------------------------------
fusionauth-search.transport-port=9020
fusionauth-search.http-port=9021
fusionauth-search.memory=512M
fusionauth-search.additional-java-args=
# Special values include: _local_, _site_. Values can be combined in a comma separated list.
fusionauth-search.hosts=_local_
# Specify the location of your FusionAuth Search Engine servers. Multiple values may be specified using a comma separator.
# This configuration is used by ElasticSearch to configure clustering. The specified port should be the configured value
# for 'fusionauth-search.transport-port'.
#
# Single host example: localhost:9020
# Multiple hosts example: localhost:9020,192.168.1.42:9020
fusionauth-search.servers=localhost:9020
# Specify the full path to the ElasticSearch data directory. This defaults to /usr/local/fusionauth/data/search/esv6
# on Linux/Unix and %FUSIONAUTH_HOME%\data\search\esv6 on Windows if not specified
fusionauth-search.data-directory=
#------------------------------------------------------------------------------
# fusionauth-app
# - Required on each node running FusionAuth App webservice
#------------------------------------------------------------------------------
# Optionally specify an addressable URL or IP address to access this node from other FusionAuth nodes.
# - In most cases this should be left empty and it will be determined at runtime.
# - Ideally this is a site local IP address that is not publicly routable but accessible from other FusionAuth nodes.
fusionauth-app.url=
# Specify the search engine type, accepted values are `database` and `elasticsearch`.
# When configuring the search engine type to `elasticsearch`, you must configure the `fusionauth-app.search-servers` property as well.
fusionauth-app.search-engine-type=database
# Specify the location of your FusionAuth Search servers. Multiple values may be specified using a comma separator.
# This configuration is used by FusionAuth App to connect to the ElasticSearch nodes. The specified port should be the
# configured value for 'fusionauth-search.http-port'.
#
# Single host example: http://localhost:9021
# Multiple hosts example: http://localhost:9021,http://192.168.1.42:9021
#fusionauth-app.search-servers=http://localhost:9021
# Specify the management and HTTP ports for Tomcat
fusionauth-app.management-port=9010
fusionauth-app.http-port=9011
fusionauth-app.https-port=9013
fusionauth-app.ajp-port=9019
# Specify the memory size here. You can use M for megabytes and G for gigabytes
fusionauth-app.memory=512M
# Specify any additional JVM arguments here
fusionauth-app.additional-java-args=
# Cookie Same Site Policy
# - Possible values [Strict, None, Lax]
#
# During development you may want to set this value to None if you're on http and a server is returning you cross domain cookies over https.
fusionauth-app.cookie-same-site-policy=Lax
# Runtime Mode. During development use, 'development' this will allow you to utilize maintenance mode.
# - Once you move into production, use 'production', this will disable maintenance mode.
# - Possible values [production, development]
fusionauth.runtime-mode=development
After some playing around and restarting this and that, I tried again and received this error, "The database and schema exist, but for some reason the ordinary user you specified cannot connect to it. Perhaps the user already existed and you provided the wrong password. The error from the database was [Access denied for user 'fusionauth'@'localhost' (using password: YES)]. "
I updated the password to what was in the config file and tried again and it went back to the superuser error of "Unable to connect to your database using the superuser username and password, verify your connection information. If it is correct, make sure the database is running before continuing."
There are two instances of MySql running, I believe. One is a Plesk SQL Server process, and the other is a standard MySql process. In the MySQL datadir path statement in my.ini file it is pointing to the path I mentioned in #4 above. When I try to log in to the mysql.exe in Plesk SQL server directory I get an access denied error. When logging into the mysql.exe in MySQL directory I'm successful. Is FusionAuth somehow trying to authenticate with superuser to the Plesk instance?