I’ve just retested and works okay for me. Have you installed 5.0.1 patches? Check here: https://www.open-emr.org/wiki/index.php/OpenEMR_Patches and be careful if you have custom code. The files for portal are what you need so just use them if you need to. Just let me know what patch version you are on now if any for others info.
hi @sjpadgett i follow your advices , I installed patch for 5.0.1 but the problem still there
i uploaded a small videos showing the problem
–https://drive.google.com/file/d/16jAg_HEZcdotit-Md2sawTNIy-PMe0bu/view?usp=sharing http://sendvid.com/rrv2ozro
Has to be something with your install. Check file permissions and user:group permissions in openemr/portal/patient directory if on ubuntu. Check browser console to see if the fetch returns a 404 or 500 error. Check php error logs for clues.
Ray if I remember correctly, you got this to work when you reinstalled. Is that correct?
I saw portal folder, the folder has permission 775 and ec2-user and apache group
but… the files inside the folder “Portal” has diferentes permission and groups, some files has permission 644 with ec2-user and apache group, and other files has permission 664 with ec2-user and groups ec2-user, is it correct ?
I’ll send you a screen capture
I assume this is Alpine in a docker container. No matter but i’m not sure what is in the apache group so suggest doing a recursive chown -R ec2-user:ec2-user on portal directory.
edit: are you able to log in as portal patient?
Still not working but I have not loaded the latest files.
Okay thanks. I don’t understand what is missing. All my testing works okay so i’ll try test some more.
hi Jerry, if I remember from another thread that the web server doesn’t like the leading /openemr in the path name?
That’s true but i’m pretty sure one of the patches adds a url test for making sure web_root is properly parsed for a relative endpoint. The browser should take care of the rest of inserting correct domain. @geromoss Really do need the browser console error to know for sure.
1 Like
I just retested again against all our demos in demo farm including Alpine 3.7. All are okay. @geromoss Can you e-mail me your sites portal url so I can test myself? sjpadgett@gmail.com
i changed permission on Portal directory for ec2-user:ec2-user and still the same problem, i’m not using Alpine neither Docker container, just downloaded packed from oficial website OpenEMR version http://sourceforge.net/projects/openemr/files/OpenEMR%20Current/5.0.1.6/openemr-5.0.1.tar.gz
thank you @sjpadgett i send you an email with the link
I used a second browser to avoid session conflicts and it still failed. However I noticed in openemr, when I reset the browser credentials for my test user, the username in the pop-up was different than the username in the demographics for CMS Portal Login for this patient. When I changed this CMS Portal Login value to match the one autocreated (?), I was able to get it to work… Does that make sense?
I do know that only one portal should be enabled. I’ll check code but maybe i’m grabbing the wrong credentials. Anyway this is a clue, thanks. @geromoss Have you got more than one portal enabled in Globals?
@geromoss For some reason portal can’t access the patientdata restful endpoint. Must be something with server config. Maybe need to add server directory permissions for openemr/portal/patient directory or .htaccess is turn off. Are you behind a proxy, reverse proxy or load balancer that may be rewriting the url? Be sure to uncheck Portal Uses Server Base Path (internal) in Globals now that you did some changes and try. Once again, can you log in as a portal patient? Otherwise, I don’t know how to help.
@rmagauran Do you know if cms portal uses patient_access_onsite for passwords? If so then that’s an issue for running dual portals which by the way, the demo farm has all portals turned on so that may not be an issue.
Anyway, I can’t recreate so i’m at a loss.
Hi,
All portals should be able to run simultaneously.
Left related comments on this thread:
-brady
1 Like
not working on demo server while in local system it is working fine
/openemr/portal/patient/onsitedocuments?pid=10
this above url is giving error 404
can anyone suggest please ?
i Solved it!
the problem is Amazon Ec2 has desactivated .htaccess for default and some file in folder openEmr have different permission and user group for default , so what i do was: change configuration in apache, delete complete folder OpenEMR, download again OpenEMER, unzip it and change permission and group recursive files and folders OpenEMR.
Details Instructions:
- go to configuration Apache (in my server Amazon Ec2 is located in /etc/httpd/conf/httpd.conf) sudo nano /etc/httpd/conf/httpd.conf
- go to DocumentRoot “/var/www/html” and looking for AllowOverride None
- changed AllowOverride None to AllowOverride All <- very important
- go to terminal /var/www/html and delete folder openEMR
- use wget http://www…tar.gz to download openEMR last version
- follow instruction to unzip OpenEMR zip in folder
- very importante change permission and group folder OpenEMR that correspond, in my case i use : sudo chown -R ec2-user:apache /var/www/html/openemr
- go to openEmr page setup.php and following instructions
- FIX IT!!! now patients have self-registration
THANK TO EVERYDOY for your HELP , i think you should add text in install instructions page wiki use a command recursive like: sudo chown -R [user]:[group] /var/www/html/openemr because for some reason when unzip openEMR it has differents groups and permission default in some files PHP and CSS
thank you
As per the screenshot, I have the patient portal under 443 SSL of third party wildcard certificate and getting this URL connection error for certain screens such as My Profile, My Messages and My Documents. Please see attached the relevant files
.htaccess (217 Bytes)
httpd.conf (21.3 KB)
httpd-ssl.conf (13.1 KB)
httpd-vhosts.conf (3.9 KB)
openemr.conf (1.0 KB)
. Read form posts and tried everything suggested and discussed on Sat call. Help greatly appreciated. Thanks!
For anyone getting 404 errors where the redirect is working, ensure you’re not using aliasing/redirecting directly into the portal directory from apache.
portal must be part of the URL e.g. https://domain/portal or https://domain/openemr/portal and not an alias of say DocumentRoot "C:/path/to/openemr/portal"
Portal is not a stand alone app but I do plan to allow portal to emulate as if a gateway in future.
1 Like