did you open port 8080 on your firewall? This is the first thing that comes to my mind. If it is working fine then the path to the outside is blocked. You can run port detective to see what ports you have opened to the web.
Actually, it looks like the server is there, just the directory location/vhosts etc… is wrong.
What kind of installation is this?
I noticed when logging into the domain name at port 8080 it DOES ask for a username and password, so it IS doing something, not just timing out. Not meaning to ask a dumb question, but what changed?
There is a tiny possibility that if you truly didn’t do anything to your setup, and you have not been hacked, then your router COULD be *partially* screwing up resolving port 8080. I HAVE seen that before. Routers and switches are flaky things. I would isolate/change the gear involved, or even load up a new or working backup install on another computer to test the system itself before digging into the software side of stuff. Of course, you could just resolve to the domain name and use your login to see if you get index access to the server. Do you have any other sites or applications on that server (sub domain or different domain name) that you can access? Perhaps you can pop a page other than openEMR into the htdocs and test for access.
ok, we know you can disregard that because your server is yours and has no malware. So you can ignore the warning.
However, since your server is a windows server use IE, and tell me what you get when you use http://localhost/openemr/?site=yoursite
I will be online to help troubleshoot if you want
replace “yoursite” with “default” or the name of your site. depending on your set up, but do not post it here. Just tell me the result
looks like you are trying to access your site from a mac or linux computer (mayb?)
Just let us start at beginning. start with the windows server itself. if needed email me at sourceforge.net
Actually, I have to disagree here. The warning is from Google and should not be ignored. It is reporting that the site contains content from a known malware source (forghost.3322.org).
It’s quite possible that (if the original reporter is a legitimate user) his site has been compromised.
Looking a little more closely, the main pages for this site (www.emr4doctors.com/www.emr4patients.com) also appear to have malicious code embedded. You can see that the code is causing the client browser to pull in content from the malware site:
Sorry, but I don’t think so. This looks like a classic example of a drive-by attack. Also, your “Free DNS” service 3322.org has a history of being used in these types of schemes.
In fact, I’d go so far as to caution others here to avoid this poster’s site(s) until this issue has been properly addressed. It would also be wise to run a malware scan if you visited any of the associated urls.
This poses a serious risk to the numerous and unsuspecting Windows users visiting this forum, especially those that have sensitive data like patient information on their Windows machines.
For the sourceforge user, I only see: https://me.yahoo.com/a/0YPc1OBv
I do not know who this user is, however Tony has referred to this user as Don in the past. Would be nice to get clarification that this user is known in the community so everybody isn’t worried. If can’t get clarification or verify who this user is, then it’s easy to delete the posts that contain the risky links.
Hi,
If I don’t get confirmation on this user by tomorrow (either by the user themselves or somebody who knows this user), then will delete the posts here that contain the apparent bad links.
thanks,
-brady
I did not know that my membership was not displaying my email or other information. Thanks for the phone call regarding my information. You welcome to remove all of my posts and any code changes I suggested. We had a conflict with a webcam that was talking to port 8080 after all it was not an outside threat. Thank you.
There’s no reason to remove your posts if we know who you are. Just wanted to make sure an anonymous user wasn’t posting links to a malware site, which is not the case. What is going on with the issue that aaversa brought up above regarding the apparent code on your site: